HCL BigFix Compliance is potentially affected by Oracle database credentials stored at endpoint

published 2024-05-07 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-21046

cvss: 6.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.2%; EPSS 0.2% chance of exploitation in 30 days, percentile 6%
public exploits: 0; none known

Database scanning using username and password stores the credentials in plaintext or encoded format within files at the endpoint. This has been identified as a significant security risk. This will lead to exposure of sensitive information for unauthorized access, potentially leading to severe consequences such as data breaches, unauthorized data manipulation, and compromised system integrity.

CISA SSVC

Exploitation: none
Automatable: no
Technical impact: total
Assessed: 2 y ago (2024-07-19)

Exploit prediction

0.17% chance of exploitation in the next 30 days, higher than 6% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.5	CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H

Affected products

HCL Software BigFix Compliance
hcltech bigfix_compliance

Classification

Weakness

CWE-522 Insufficiently Protected Credentials

References

support.hcltechsw.com /csm?id=kb_article&sysparm_article=KB0112963

Sources

CVE List CVE-2024-23551
NVD CVE-2024-23551

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary