Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 25 Apr 2014 20:57:17 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12710653.1398459338390.183867.1398459437072@arcas>
In-Reply-To: <JIRA.12710653.1398459338390@arcas>
References: <JIRA.12710653.1398459338390@arcas>
Subject: [jira] [Created] (ACCUMULO-2738) Potential null pointer reference
 in ConfigCommand#execute()
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Ted Yu created ACCUMULO-2738:
--------------------------------

             Summary: Potential null pointer reference in ConfigCommand#execute()
                 Key: ACCUMULO-2738
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2738
             Project: Accumulo
          Issue Type: Bug
            Reporter: Ted Yu
            Priority: Minor


Starting at line 210 :
{code}
        if (dfault != null && key.toLowerCase().contains("password")) {
          siteVal = sysVal = dfault = curVal = curVal.replaceAll(".", "*");
        }
        if (sysVal != null) {
          if (defaults.containsKey(key) && !Property.getPropertyByKey(key).isExperimental()) {
            printConfLine(output, "default", key, dfault);
{code}
Comparing dfault with null implies that dfault may be null.
If that is the case, we would get null pointer dereference in the call to printConfLine() at line 215 where dfault.replace() is called.


--
This message was sent by Atlassian JIRA
(v6.2#6252)