Raw vector
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2024-38327 is a medium-severity Inclusion of Sensitive Information in Source Code (CWE-540) vulnerability in Ibm Analytics Content Hub. Its CVSS base score is 6.8 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Code Repositories (T1213.003); ranked at the 20th 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 AC-3 (Access Enforcement) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
IBM Analytics Content Hub versions 2.0, 2.1, 2.2, and 2.3 are affected by CVE-2024-38327, a vulnerability involving information exposure through an exposed JavaScript source map. This exposure allows potential attackers to read and debug the JavaScript code used in the application's API, facilitating further attacks. The issue is classified under CWE-540 and has a CVSS v3.1 base score of 6.8 (AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:H), indicating medium severity with high impacts on confidentiality, integrity, and availability.
Exploitation requires network access, low attack complexity, high privileges (PR:H), and user interaction (UI:R). A privileged user, such as an authenticated administrator or similar role, could be targeted to access the exposed source map, enabling them to analyze and reverse-engineer the API's JavaScript logic. Successful exploitation could lead to significant information disclosure and subsequent attacks, potentially compromising the confidentiality, integrity, and availability of the application.
IBM has published an advisory detailing the vulnerability at https://www.ibm.com/support/pages/node/7234122, which security practitioners should consult for specific mitigation steps, such as applying patches or configuration changes to prevent source map exposure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-54770
Vulnerability Data
IBM Analytics Content Hub 2.0, 2.1, 2.2, and 2.3 is vulnerable to information exposure and further attacks due to an exposed JavaScript source map which could assist an attacker to read and debug JavaScript used in the application's API.
- 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 static analysis locate hard-coded sensitive values before code is deployed.
Enforces access so that source containing embedded secrets cannot be reached by unauthorized parties.
Engineering principles require secrets to be externalized rather than embedded in source.
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 source code.
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.
Directly restricts access to source code, preventing exposure of embedded sensitive information.
Secure coding standards explicitly prohibit hard-coding credentials or sensitive data.
Classification helps identify source code containing sensitive data so it can be protected.
Access control limits who can view or retrieve source code that may contain secrets.
Secure SDLC practices include removing secrets from code before commit or deployment.
Environment separation reduces risk of accidental exposure but does not address secrets already in code.