dbcve.org
Resource Allocation Without LimitsWeakness · CWE-770

CVE-2024-33495

MEDIUM · 6.5 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 →
71/100
Remediation priority · Elevated
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 does not properly limit the size of specific logs. This could allow an unauthenticated remote attacker to exhaust system resources by creating a great number of log entries which could potentially lead to a denial of service condition. A successful exploitation requires the attacker to have access to specific SIMATIC RTLS Locating Manager Clients in the deployment.

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 vulnerability is a resource exhaustion issue where the SIMATIC RTLS Locating Manager application fails to properly limit the size of specific logs. An unauthenticated remote attacker with access to specific RTLS Locating Manager Clients can generate excessive log entries, filling up disk space or system resources and causing denial of service.

MitigationUpdate SIMATIC RTLS Locating Manager to version V3.0.1.1 or later per Siemens security advisory. If immediate patching is not possible, implement network segmentation to restrict access to RTLS Manager Clients.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Identify if SIMATIC RTLS Locating Manager is installed
    Check installed programs or services for SIMATIC RTLS Locating Manager or RTLS Locating Manager. On Windows, review Add/Remove Programs or check Program Files for Siemens\SIMATIC_RTLS folders.
    Affected if The software is present on the system
  2. Determine the installed version of SIMATIC RTLS Locating Manager
    Check the application version through the Windows installed programs list, the software itself (typically in Help > About or similar), or registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\ if accessible. Note the exact version number.
    Affected if Version is found to be below V3.0.1.1 (such as V3.0.0.x or earlier releases)
  3. Verify network accessibility of RTLS Locating Manager Client interfaces
    Review network configuration, firewall rules, and exposed ports. Check if the RTLS Locating Manager service port (commonly TCP ports associated with RTLS communication) is accessible from untrusted networks or external interfaces.
    Affected if RTLS Manager Client interfaces are reachable from network segments accessible to unauthenticated remote attackers
  4. Inspect log configuration and disk space consumption
    Locate log directories used by SIMATIC RTLS Locating Manager (typically under the installation folder or Windows Logs). Check current log file sizes, count of log entries, and available disk space on volumes hosting logs.
    Affected if Log files are excessively large, show rapid growth, or disk space is being consumed abnormally by RTLS-related logs

You are affected if SIMATIC RTLS Locating Manager is installed with a version prior to V3.0.1.1 and the RTLS Manager Client service is network-accessible to unauthenticated 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

Update SIMATIC RTLS Locating Manager to version V3.0.1.1 or later per Siemens security advisory. If immediate patching is not possible, implement network segmentation to restrict access to RTLS Manager Clients.

Recommended fix High confidence

V3.0.1.1

  1. Upgrade SIMATIC RTLS Locating Manager (6GT2780-0DA00) to version V3.0.1.1
  2. Upgrade SIMATIC RTLS Locating Manager (6GT2780-0DA10) to version V3.0.1.1
  3. Upgrade SIMATIC RTLS Locating Manager (6GT2780-0DA20) to version V3.0.1.1
  4. Upgrade SIMATIC RTLS Locating Manager (6GT2780-0DA30) to version V3.0.1.1
  5. Upgrade SIMATIC RTLS Locating Manager (6GT2780-1EA10) to version V3.0.1.1
  6. Upgrade SIMATIC RTLS Locating Manager (6GT2780-1EA20) to version V3.0.1.1
  7. Upgrade SIMATIC RTLS Locating Manager (6GT2780-1EA30) to version V3.0.1.1
  8. Obtain the update from the Siemens CERT portal at cert-portal.siemens.com

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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