dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2024-30208

MEDIUM · 6.3 CVSS v3.1 Published 2024-05-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/100
Remediation priority · Elevated
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
A vulnerability has been identified in SIMATIC RTLS Locating Manager (6GT2780-0DA00) (All versions < V3.0.1.1), SIMATIC RTLS Locating Manager (6GT2780-0DA10) (All versions < V3.0.1.1), SIMATIC RTLS Locating Manager (6GT2780-0DA20) (All versions < V3.0.1.1), SIMATIC RTLS Locating Manager (6GT2780-0DA30) (All versions < V3.0.1.1), SIMATIC RTLS Locating Manager (6GT2780-1EA10) (All versions < V3.0.1.1), SIMATIC RTLS Locating Manager (6GT2780-1EA20) (All versions < V3.0.1.1), SIMATIC RTLS Locating Manager (6GT2780-1EA30) (All versions < V3.0.1.1). The "DBTest" tool of SIMATIC RTLS Locating Manager does not properly enforce access restriction. This could allow an authenticated local attacker to extract sensitive information from memory.

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 · high confidence

The DBTest tool in SIMATIC RTLS Locating Manager versions prior to V3.0.1.1 does not properly enforce access restrictions, allowing an authenticated local attacker to extract sensitive information from memory.

MitigationUpgrade SIMATIC RTLS Locating Manager to version V3.0.1.1 or later to address the improper access control in the DBTest tool.

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

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Locate the SIMATIC RTLS Locating Manager installation
    Check the program files directory or application installation path for the SIMATIC RTLS Locating Manager software, typically found under Siemens\SIMATIC_RTLS or similar Siemens program folders
    Affected if The software is installed on the system
  2. Determine the installed version of SIMATIC RTLS Locating Manager
    Open the software or check the program properties/About dialog to find the exact version number, or look for version information in the installation directory
    Affected if The version is displayed as anything prior to V3.0.1.1 (such as V3.0, V2.x, or earlier)
  3. Locate the DBTest tool executable or component
    Search for files named DBTest.exe or DBTest within the SIMATIC RTLS Locating Manager installation directory
    Affected if The DBTest executable exists in the installation folder
  4. Verify the DBTest tool is accessible to local users
    Check file system permissions on the DBTest executable to see if standard local users have execute or read access
    Affected if Local authenticated users can access and run the DBTest tool

A user is affected if SIMATIC RTLS Locating Manager version is installed and the DBTest tool is present with version prior to V3.0.1.1, allowing potential sensitive memory extraction by local authenticated attackers

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade SIMATIC RTLS Locating Manager to version V3.0.1.1 or later to address the improper access control in the DBTest tool.

Recommended fix High confidence

V3.0.1.1 or later

  1. 1. Identify the currently installed version of SIMATIC RTLS Locating Manager by accessing the software or checking system documentation.
  2. 2. Download SIMATIC RTLS Locating Manager version V3.0.1.1 or later from the official Siemens support portal (support.industry.siemens.com) or your existing Siemens software distribution channel.
  3. 3. Back up the current configuration and data according to your organization's backup procedures for industrial control systems.
  4. 4. Apply the upgrade to all affected instances of SIMATIC RTLS Locating Manager (models 6GT2780-0DA00, 6GT2780-0DA10, 6GT2780-0DA20, 6GT2780-0DA30, 6GT2780-1EA10, 6GT2780-1EA20, 6GT2780-1EA30).
  5. 5. After upgrading, verify that the DBTest tool now properly enforces access restrictions and that sensitive information cannot be extracted by unauthorized authenticated users.
  6. 6. Document the upgrade in the system's change management system.
Caveat Review Siemens release notes for any compatibility considerations before upgrading industrial control system software

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-30208 — 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-30208 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