cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-12298) Privacy Violation - Heap Inspection
Date Wed, 27 Jul 2016 21:34:20 GMT


Jonathan Ellis updated CASSANDRA-12298:
    Issue Type: Sub-task  (was: Bug)
        Parent: CASSANDRA-12334

> Privacy Violation - Heap Inspection
> -----------------------------------
>                 Key: CASSANDRA-12298
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Eduardo Aguinaga
>            Assignee: Jason Brown
> Overview:
> In May through June of 2016 a static analysis was performed on version 3.0.5 of the Cassandra
source code. The analysis included 
> an automated analysis using HP Fortify v4.21 SCA and a manual analysis utilizing SciTools
Understand v4. The results of that 
> analysis includes the issue below.
> Issue:
> In the file on line 89 a string object is used to store sensitive data.
String objects are immutable and should not be used to store sensitive data. Sensitive data
should be stored in char or byte arrays and the contents of those arrays should be cleared
ASAP. Operations performed on string objects will require that the original object be copied
and the operation be applied in the new copy of the string object. This results in the likelihood
that multiple copies of sensitive data will be present in the heap until garbage collection
takes place.
> The snippet below shows the issue on line 89:
>, lines 87-90:
> {code:java}
> 87 public Optional<String> getPassword()
> 88 {
> 89     return Optional.fromNullable((String)options.get(IRoleManager.Option.PASSWORD));
> 90 }
> {code}

This message was sent by Atlassian JIRA

View raw message