dbcve.org
Incorrect Permission AssignmentWeakness · CWE-732

CVE-2024-33499

CRITICAL · 9.1 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 →
97/100
Remediation priority · Urgent
Remotely reachable 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 affected application assigns incorrect permissions to a user management component. This could allow a privileged attacker to escalate their privileges from the Administrators group to the Systemadministrator group.

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

This is a privilege escalation vulnerability in the SIMATIC RTLS Locating Manager user management component, where incorrect permission assignments allow an attacker with Administrator privileges to elevate to the Systemadministrator role. The flaw exists in all versions prior to V3.0.1.1 across multiple product variants.

MitigationUpgrade SIMATIC RTLS Locating Manager to version V3.0.1.1 or later to resolve the permission misconfiguration in the user management component.

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

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

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. Confirm SIMATIC RTLS Locating Manager is installed
    Look for the application in the Windows Start Menu, Program Files, or check Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\SIMATIC_RTLS_Locating_Manager
    Affected if The application is present on the system
  2. Determine the installed version
    Right-click the application executable (LocatingManager.exe), select Properties, then view the Details tab for the File Version; alternatively, check the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\SIMATIC_RTLS_Locating_Manager\Version
    Affected if The version is earlier than V3.0.1.1 or the version cannot be determined (unknown versions should be treated as vulnerable)
  3. Verify access to the user management component
    Log into the SIMATIC RTLS Locating Manager web interface or desktop application and navigate to the User Administration or User Management settings panel
    Affected if User management functionality is accessible and configurable
  4. Check current user role privileges
    In the user management panel, view the list of defined roles and the currently logged-in user account's assigned role
    Affected if The current user has Administrator privileges but does not yet have Systemadministrator role, and the Systemadministrator role is defined in the system

A user is affected if SIMATIC RTLS Locating Manager version V3.0.1.1 or later is NOT installed and the user has Administrator access to the user management component, enabling potential elevation to Systemadministrator.

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 resolve the permission misconfiguration in the user management component.

Recommended fix High confidence

SIMATIC RTLS Locating Manager V3.0.1.1

  1. 1. Identify the current version of SIMATIC RTLS Locating Manager installed on the system
  2. 2. Download SIMATIC RTLS Locating Manager version V3.0.1.1 from the official Siemens cert-portal or support website
  3. 3. Review Siemens installation/upgrade documentation for SIMATIC RTLS Locating Manager
  4. 4. Perform a backup of current system configuration and data as recommended by Siemens upgrade procedures
  5. 5. Install version V3.0.1.1 following Siemens standard upgrade process for the specific product model (6GT2780-0DA00, 6GT2780-0DA10, 6GT2780-0DA20, 6GT2780-0DA30, 6GT2780-1EA10, 6GT2780-1EA20, or 6GT2780-1EA30)
  6. 6. Verify the upgrade was successful by checking the installed version
  7. 7. Confirm the user management component now has correct permissions and privilege escalation from Administrators to Systemadministrator is no longer possible

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

Have this fixed 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 help mitigating

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-33499 — 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-33499 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