dbcve.org
Insufficiently Protected CredentialsWeakness · CWE-522

CVE-2024-33496

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). Affected SIMATIC RTLS Locating Manager Report Clients do not properly protect credentials that are used to authenticate to the server. This could allow an authenticated local attacker to extract the credentials and use them to escalate their access rights from the Manager to the Systemadministrator role.

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 vulnerability in SIMATIC RTLS Locating Manager Report Clients (multiple 6GT2780 variants) fails to properly protect authentication credentials used for server communication. An authenticated local attacker with Manager role can extract these unprotected credentials and use them to escalate privileges to Systemadministrator role.

MitigationUpgrade all affected SIMATIC RTLS Locating Manager installations to version V3.0.1.1 or later per Siemens advisory. Review and rotate any credentials that may have been exposed prior to patching.

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. Identify installed SIMATIC RTLS product variant
    Locate the installed SIMATIC RTLS Locating Manager Report Client and note the model number (6GT2780-x variant) in the system inventory or installed software list
    Affected if The product is a SIMATIC RTLS Locating Manager Report Client with a 6GT2780 model number and the version is below V3.0.1.1
  2. Check installed software version
    Access the software version information through the product's about dialog, installation directory metadata, or Windows Programs and Features entry for the SIMATIC RTLS Locating Manager component
    Affected if The displayed version is earlier than V3.0.1.1 (for example, V3.0.0.x or prior releases)
  3. Verify Manager role access exists
    Check if any local user account has Manager role privileges within the SIMATIC RTLS Locating Manager application by reviewing the user role configuration
    Affected if A local user with Manager role account exists and is able to log into the Locating Manager application
  4. Confirm server communication is configured
    Review the Locating Manager configuration to determine if server communication credentials have been stored or configured for connecting to the backend server
    Affected if Server communication is enabled and credentials are stored locally in the application configuration

A user is affected if they have a SIMATIC RTLS Locating Manager Report Client (6GT2780 variant) installed with a version earlier than V3.0.1.1 and the application has server communication credentials configured for a user with Manager role access.

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 all affected SIMATIC RTLS Locating Manager installations to version V3.0.1.1 or later per Siemens advisory. Review and rotate any credentials that may have been exposed prior to patching.

Recommended fix High confidence

V3.0.1.1

  1. Identify the specific SIMATIC RTLS Locating Manager product variant (6GT2780-0DA00, 6GT2780-0DA10, 6GT2780-0DA20, 6GT2780-0DA30, 6GT2780-1EA10, 6GT2780-1EA20, or 6GT2780-1EA30) currently deployed
  2. Obtain the fixed version V3.0.1.1 from Siemens via their official support channels or cert-portal.siemens.com
  3. Plan and schedule a maintenance window for the upgrade
  4. Backup all existing configuration data and credentials for the current RTLS Locating Manager installation
  5. Upgrade the SIMATIC RTLS Locating Manager to version V3.0.1.1 following Siemens installation documentation
  6. After upgrade, verify that credentials are now properly protected and cannot be extracted by local authenticated users
  7. Confirm the Manager to Systemadministrator role escalation vulnerability is resolved

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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