[jira] [Updated] (ACCUMULO-2738) Potential null pointer reference in ConfigCommand#execute()

["Josh Elser (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/ACCUMULO-2738?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Josh Elser updated ACCUMULO-2738:
---------------------------------
    Fix Version/s:     (was: 1.5.2)
                   1.5.3

> Potential null pointer reference in ConfigCommand#execute()
> -----------------------------------------------------------
>
>                 Key: ACCUMULO-2738
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2738
>             Project: Accumulo
>          Issue Type: Bug
>          Components: shell
>    Affects Versions: 1.4.0, 1.5.0, 1.6.0
>            Reporter: Ted Yu
>            Priority: Minor
>              Labels: newbie
>             Fix For: 1.5.3, 1.6.1, 1.7.0
>
>
> 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.3.4#6332)