dbcve.org
CockpitApplication · Tnbmobil

CVE-2024-1272

HIGH · 7.5 CVSS v3.1 Published 2024-06-05
Fix available
A fix is available. Upgrade to 0.251.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a hardcoded sensitive information vulnerability in TNB Mobile Solutions Cockpit Software. The software contains embedded sensitive data (such as credentials, API keys, tokens, or passwords) directly in the source code, which attackers can retrieve. The vulnerability is patched in version v0.251.1 and later.

MitigationUpgrade Cockpit Software to version v0.251.1 or later. Additionally, conduct a code review to identify and remove any hardcoded sensitive data, and implement a secrets management solution (e.g., environment variables, vault) for future deployments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
CockpitApplication
Affected:< 0.251.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed version of Tnbmobil Cockpit
    Locate the software installation directory and check the version file, about screen, or version command output. Look for version indicators such as version metadata, changelog, or the application binary that displays the version number.
    Affected if The installed version is lower than 0.251.1 (e.g., 0.250.0, 0.240.0, etc.)
  2. Inspect source code for hardcoded credentials
    Search the application source code files (configuration files, script files, application binaries, or any deployable artifacts) for strings that resemble credentials, API keys, tokens, or passwords. Use grep or similar tools to search for patterns like 'password=', 'api_key=', 'token=', 'secret=', or base64-encoded strings that may decode to sensitive data.
    Affected if Any hardcoded sensitive data (credentials, API keys, tokens, or passwords) is found embedded directly in the source code or configuration files of the Tnbmobil Cockpit installation
  3. Check for embedded secrets in configuration files
    Examine all configuration files, properties files, YAML files, or XML files within the Tnbmobil Cockpit installation directory. Look for plaintext passwords, API keys, authentication tokens, or other secrets stored directly in these files.
    Affected if Sensitive credentials or API keys are found stored in plaintext within configuration files distributed with the software

You are affected if Tnbmobil Cockpit version is below 0.251.1 AND the source code or configuration files contain embedded credentials, API keys, tokens, or passwords.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 0.251.1 or later
Fixed in 0.251.1
Interim mitigation

Upgrade Cockpit Software to version v0.251.1 or later. Additionally, conduct a code review to identify and remove any hardcoded sensitive data, and implement a secrets management solution (e.g., environment variables, vault) for future deployments.

Recommended fix Moderate confidence

Cockpit v0.251.1

  1. 1. Identify all deployments of Cockpit software in your environment running versions before 0.251.1
  2. 2. Back up current configurations and data before upgrading
  3. 3. Obtain Cockpit version 0.251.1 or later from the official vendor (TNB Mobile Solutions)
  4. 4. Upgrade Cockpit software to version 0.251.1 following vendor-provided upgrade instructions
  5. 5. After upgrade, verify that sensitive information (credentials, API keys, tokens) is no longer hardcoded in source code and is properly managed via secure methods (environment variables, secrets management)
  6. 6. Review logs and access patterns to confirm no unauthorized access to embedded sensitive data occurred prior to the upgrade
Caveat Review vendor release notes for any breaking changes between your current version and 0.251.1 before upgrading in production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cockpit Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1272 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1272 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data