CVE-2024-1272: Information Disclosure to Source Code in TNB Mobile Solutions' Cockpit Software
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.
Security readout for executives and security teams
Plain-English summary
TNB Mobile Solutions Cockpit Software before v0.251.1 may expose sensitive data embedded in source code. An unauthenticated remote attacker could retrieve that information, creating a confidentiality risk. The sources do not state that integrity or availability are affected.
Executive priority
Treat this as a high-priority confidentiality issue if Cockpit Software is in use. The business risk is exposure of embedded sensitive data, potentially including credentials or operational secrets, though the sources do not specify the exact data type.
Technical view
CVE-2024-1272 is CWE-540, Inclusion of Sensitive Information in Source Code, affecting Cockpit Software before v0.251.1. CVSS 3.1 is 7.5: network reachable, low complexity, no privileges, no user interaction, unchanged scope, high confidentiality impact only.
Likely exposure
Exposure is limited to organizations running TNB Mobile Solutions Cockpit Software versions before v0.251.1. The bundle provides no CPEs, deployment details, or default exposure assumptions, so asset owners must verify installed versions directly.
Exploitation context
The CVE is not listed as KEV in the supplied bundle, and the provided sources do not claim active exploitation. The CVSS vector indicates exploitation would not require authentication or user interaction, but no exploit maturity evidence is provided.
Researcher notes
Evidence is concise and version-focused. The affected range is before v0.251.1, CWE-540, CVSS 7.5. The bundle marks one USOM reference as a broken link, and no public exploit, CPE, product deployment model, or detailed advisory text is provided.
Mitigation direction
Identify all Cockpit Software deployments and record exact versions.
Move systems off versions before v0.251.1 where vendor guidance supports it.
Review vendor and government advisories for the approved remediation path.
Rotate any secrets that may have been embedded or exposed.
Restrict network access to Cockpit Software until remediation is complete.
Validation and detection
Confirm deployed Cockpit Software versions are v0.251.1 or later.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-540: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-540 · source CWE mapping
Inclusion of Sensitive Information in Source Code
Inclusion of Sensitive Information in Source Code represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.