The Kiuwan Local Analyzer (KLA) Java scanning application contains several hard-coded secrets in plain text format. In some cases, this can potentially compromise the confidentiality of the scan results. Several credentials were found in the JAR files of the Kiuwan Local Analyzer.
The JAR file lib.engine/insight/optimyth-insight.jar contains the file InsightServicesConfig.properties, which has the configuration tokens insight.github.user as well as insight.github.password prefilled with credentials. At least the specified username corresponds to a valid GitHub account. The JAR file lib.engine/insight/optimyth-insight.jar also contains the file es/als/security/Encryptor.properties, in which the key used for encrypting the results of any performed scan.
This issue affects Kiuwan SAST: <master.1808.p685.q13371
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
Because the information is stored in cleartext (i.e., unencrypted), attackers could potentially read it. Even if the information is encoded in a way that is not human-readable, certain techniques could determine which encoding is being used, then decode the information. When organizations adopt cloud services, it can be easier for attackers to access the data from anywhere on the Internet. In some systems/environments such as cloud, the use of “double encryption” (at both the software and hardware layer) might be required, and the developer might be solely responsible for both layers, instead of shared responsibility with the administrator of the broader system/environment.