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
Metrics
Affected Vendors & Products
Solution
The vendor provides a patched version master.1808.p685.q13371 which should be installed immediately. See the changelog from the vendor: https://www.kiuwan.com/docs/display/K5/%5B2024-05-30%5D+Change+Log * XML External Entity Injection => CVE-2023-49110 is SAS-6851 fixed on release 2024-02-06 * Services Running as Root => is SAS-6856 and SAS-6857 fixed on release 2024-05-15 * Reflected Cross-site-scripting => CVE-2023-49111 is SAS-6852 fixed on release 2024-02-06 * Insecure Direct Object Reference => CVE-2023-49112 is SAS-6853 fixed on release 2024-02-06 * Sensitive Data Stored Insecurely => CVE-2023-49113 is SAS-6854, SAS-6855, SAS-6858, and SAS-6859 fixed on release 2024-02-06 The following upgrade guide was provided by the vendor: https://www.kiuwan.com/docs/display/K5/Kiuwan+On-Premises+Distributed+Upgrade+Guide Although initially communicated otherwise during responsible disclosure in 2022-2023 (see timeline above), the vendor confirmed in 2024 that the SaaS/cloud version is affected and will also be patched. The patch date was 2024-02-05, version 2.8.2402.3. SEC Consult also submitted further security issues to Kiuwan, such as Docker-related configuration issues which were also fixed during our responsible disclosure. * Sensitive Data Stored Insecurely for MySQL * Sensitive Data displayed for wildfly * Containers Running as root User * Containers running in the host network * Exposure of Internal Services
Workaround
No workaround given by the vendor.
No history.

Status: PUBLISHED
Assigner: SEC-VLab
Published:
Updated: 2024-08-02T21:46:29.159Z
Reserved: 2023-11-22T11:08:37.654Z
Link: CVE-2023-49113

Updated: 2024-08-02T21:46:29.159Z

Status : Awaiting Analysis
Published: 2024-06-20T13:15:49.560
Modified: 2024-11-21T08:32:51.523
Link: CVE-2023-49113

No data.

No data.