CVE-2024-1272
Info Disclosure in Tnbmobil Cockpit ≤ 0.251.1
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-1272 is a high-severity Inclusion of Sensitive Information in Source Code (CWE-540) vulnerability in Tnbmobil Cockpit. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 31th 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.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-17033
Vulnerability Data
Inclusion of Sensitive Information in Source Code vulnerability in TNB Mobile Solutions Cockpit Software allows Retrieve Embedded Sensitive Data. This issue affects Cockpit Software: before v0.251.1.
- 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.
A.5.12 only defines and communicates a classification scheme so that protection needs can be understood; it does not itself stop source code from containing or exposing sensitive information, per the owner's rule that labeling/classification is a dependency rather than a preventer unless other controls act on it.
A.5.15 only requires defining and communicating an access control policy plus rules that reference other controls; it performs no enforcement that would stop exploitation of sensitive information left in accessible source code.
Secure SDLC practices include removing secrets from code before commit or deployment.