dbcve.org
Cleartext TransmissionWeakness · CWE-319

CVE-2024-30209

CRITICAL · 9.6 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 →
100/100
Remediation priority · Urgent
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 systems transmit client-side resources without proper cryptographic protection. This could allow an attacker to eavesdrop on and modify resources in transit. A successful exploit requires an attacker to be in the network path between the RTLS Locating Manager server and a client (MitM).

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 transmits client-side resources (likely JavaScript, CSS, or other web assets) without proper cryptographic protection (likely missing or misconfigured TLS/SSL). An attacker positioned in the network path between server and client can perform a MitM attack to eavesdrop on or modify these resources in transit.

MitigationUpgrade SIMATIC RTLS Locating Manager to version V3.0.1.1 or later to implement proper encryption for client-side resource transmission.

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

CVSS:3.1/AV:A/AC:L/PR:N/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. Identify installed SIMATIC RTLS Locating Manager version
    Open the application or check Windows Programs and Features for 'SIMATIC RTLS Locating Manager' and note the installed version number
    Affected if The installed version is older than V3.0.1.1 (for example V3.0, V2.x, or any version prior to V3.0.1.1)
  2. Determine if web interface uses unencrypted HTTP
    Attempt to access the Locating Manager web interface using http:// (not https://) - for example http://localhost or the configured server IP address
    Affected if The web interface is accessible via plain HTTP without redirect to HTTPS
  3. Verify TLS/SSL encryption is enabled on the web service
    Check the Locating Manager configuration files or web server settings for SSL/TLS protocol settings and certificate configuration
    Affected if TLS/SSL is not configured, disabled, or set to accept weak/legacy protocols only
  4. Confirm client-side resources are served over unencrypted connections
    Use a browser or network capture tool to inspect HTTP traffic when loading the Locating Manager web client - check if resources load over http:// instead of https://
    Affected if JavaScript, CSS, or other web assets are fetched over plain HTTP rather than HTTPS

A user is affected if the installed SIMATIC RTLS Locating Manager version is older than V3.0.1.1 AND the web interface or its resources are served over unencrypted HTTP connections, allowing potential MitM tampering.

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 implement proper encryption for client-side resource transmission.

Recommended fix High confidence

V3.0.1.1

  1. Identify all deployed instances of SIMATIC RTLS Locating Manager across all model numbers (6GT2780-0DA00, 6GT2780-0DA10, 6GT2780-0DA20, 6GT2780-0DA30, 6GT2780-1EA10, 6GT2780-1EA20, 6GT2780-1EA30)
  2. Verify current installed version of each instance
  3. Download SIMATIC RTLS Locating Manager V3.0.1.1 from Siemens CertPortal or official Siemens support channels
  4. Schedule maintenance window for each affected system
  5. Back up current configuration and data
  6. Upgrade each RTLS Locating Manager instance to version V3.0.1.1
  7. Verify successful installation and configuration persistence
  8. Test that all client connections now use encrypted channels
Caveat Review release notes for V3.0.1.1 to confirm no configuration or compatibility changes affect your deployment; test in non-production environment first

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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