CVE-2024-42213
Hcltech Bigfix Compliance 2.0.12
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NSummary
CVE-2024-42213 is a medium-severity Inclusion of Sensitive Information in Test Code (CWE-531) vulnerability in Hcltech Bigfix Compliance. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-13437
Vulnerability Data
HCL BigFix Compliance is affected by inclusion of temporary files left in the production environment. An attacker might gain access to these files by indexing or retrieved via predictable URLs or misconfigured permissions, leading to information disclosure.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation activities can include static analysis or code review that discovers hard-coded credentials or secrets inside test modules.
Requiring a documented development process and tools can enforce coding standards and review steps that prevent sensitive information from being left in test code.
Incorporating security into the SDLC can include standards that prohibit embedding sensitive data inside test code or applications.
Security engineering principles applied during development can require separation of test data from production secrets and removal of sensitive literals from test artifacts.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prohibit embedding secrets or sensitive data in test code and related artifacts.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development and acceptance can detect sensitive data left in test code.
Explicit control on test information directly addresses inclusion of sensitive data in test environments.
Secure SDLC mandates review of test artifacts, reducing risk of sensitive data in test code.
Secure coding standards can require scrubbing or exclusion of secrets from test modules.
Separation of dev/test/prod environments limits exposure of test code containing secrets.