dbcve.org
Uncontrolled Resource ConsumptionWeakness · CWE-400

CVE-2024-33498

MEDIUM · 5.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 →
62/100
Remediation priority · Elevated
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
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 applications do not properly release memory that is allocated when handling specifically crafted incoming packets. This could allow an unauthenticated remote attacker to cause a denial of service condition by crashing the service when it runs out of memory. The service is restarted automatically after a short time.

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 SIMATIC RTLS Locating Manager suffers from a memory management vulnerability where allocated memory is not properly released when processing specially crafted incoming packets. An unauthenticated remote attacker can send malicious packets to cause memory exhaustion, leading to service crash. The service auto-restarts after a brief period, resulting in intermittent denial of service.

MitigationUpgrade SIMATIC RTLS Locating Manager to version V3.0.1.1 or later to obtain the patched release. Implement network segmentation and firewall rules to limit exposure to untrusted network sources until the patch can be applied.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 the installed SIMATIC RTLS Locating Manager version
    Check the installed software version through the Siemens software management interface, Windows Programs and Features, or the application's About/Version dialog. Compare the version number to the fixed release V3.0.1.1.
    Affected if The installed version is lower than V3.0.1.1 or the version cannot be determined.
  2. Verify network exposure of the Locating Manager service
    Identify which network ports the SIMATIC RTLS Locating Manager service is listening on. Use netstat or a network scanner to determine if the service ports are accessible from untrusted networks.
    Affected if The service ports are exposed to untrusted or external networks without firewall protection.
  3. Check for recent unexpected service restarts
    Review Windows Event Viewer logs or the service's own log files for Event ID entries indicating unexpected crashes, restart events, or faulting of the Locating Manager process.
    Affected if Multiple unexplained service restarts or crash events are logged in the timeframe since deployment.
  4. Monitor memory usage of the Locating Manager process
    Use Task Manager or Performance Monitor to observe the memory consumption of the SIMATIC RTLS Locating Manager process over time. Look for abnormally high or continuously growing memory usage.
    Affected if The process exhibits unusually high memory consumption or memory growth patterns.

The environment is affected if SIMATIC RTLS Locating Manager version is below V3.0.1.1 AND the service is network-accessible to untrusted sources.

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 obtain the patched release. Implement network segmentation and firewall rules to limit exposure to untrusted network sources until the patch can be applied.

Recommended fix High confidence

V3.0.1.1

  1. Identify the specific SIMATIC RTLS Locating Manager model number deployed (6GT2780-0DA00, 6GT2780-0DA10, 6GT2780-0DA20, 6GT2780-0DA30, 6GT2780-1EA10, 6GT2780-1EA20, or 6GT2780-1EA30)
  2. Check the currently installed version of the Locating Manager software
  3. Obtain the update to version V3.0.1.1 or later from Siemens (refer to cert-portal.siemens.com or official Siemens support channels)
  4. Apply the update following Siemens' standard deployment procedures for SIMATIC RTLS software
  5. Verify the update was applied successfully and the service is running properly
  6. Monitor the service to confirm the memory consumption issue is resolved

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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