[Broker-J] Privacy Violation: Heap Inspection

Sensitive data (such as passwords) stored in memory can be leaked if memory is not cleared after use. Often, Strings are used store sensitive data, however, since String objects are immutable, removing the value of a String from memory can only be done by the JVM garbage collector. The garbage collector is not required to run unless the JVM is low on memory, so there is no guarantee as to when garbage collection will take place. In the event of an application crash, a memory dump of the application might reveal sensitive data.

There are several classes susceptible to this issue (e.g. ConfiguredObjectMethodAttribute, ConfiguredDerivedInjectedAttribute, ConfiguredSettableInjectedAttribute, CramMd5Base64HexNegotiator, CramMd5Base64HashedNegotiator).