dbcve.org
Simatic Rtls Locating ManagerApplication · Siemens

CVE-2020-10054

MEDIUM · 5.5 CVSS v3.1 Published 2021-11-09
Fix available
A fix is available. Upgrade to 2.12 or later.
See remediation →
57/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 (All versions < V2.12). The affected application does not properly handle the import of large configuration files. A local attacker could import a specially crafted file which could lead to a denial-of-service condition of the application service.

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 · moderate confidence

SIMATIC RTLS Locating Manager versions prior to V2.12 fail to properly handle large configuration files during import. A local attacker can import a specially crafted file to trigger a denial-of-service condition, causing the application service to become unavailable.

MitigationUpgrade to SIMATIC RTLS Locating Manager V2.12 or later to obtain the vendor patch. Coordinate upgrade during planned maintenance window and validate configuration import functionality post-upgrade.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Simatic Rtls Locating ManagerApplication
Affected:< 2.12

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
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/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. Locate the SIMATIC RTLS Locating Manager installation
    Check the program files directory (e.g., C:\Program Files\Siemens\SIMATIC_RTLS_Locating_Manager) or use Windows Add/Remove Programs to find the installed application and its version number.
    Affected if The installed version cannot be determined or is older than V2.12.
  2. Identify the installed version number
    Right-click the executable (LocatingManager.exe or similar) in the installation folder, select Properties, and review the Version tab. Alternatively, check the Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\SIMATIC_RTLS_Locating_Manager for the Version value.
    Affected if The version shown is earlier than V2.12 (e.g., V2.10, V2.0, V1.x).
  3. Confirm the configuration import feature is present
    Launch the Locating Manager application and navigate to the Settings or Configuration menu. Look for an Import/Export or Load Configuration option.
    Affected if The configuration import functionality exists and is accessible to local users.
  4. Verify the application service status
    Open Windows Services (services.msc), locate the SIMATIC RTLS Locating Manager service, and check its current status. Look for any recent crash history in Windows Event Viewer under Application logs.
    Affected if The service is currently stopped, crashed, or shows repeated failure events related to configuration loading.

You are affected if the installed SIMATIC RTLS Locating Manager version is earlier than V2.12 and the configuration import feature is present and accessible.

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
Upgrade available Upgrade to 2.12 or later
Fixed in 2.12
Interim mitigation

Upgrade to SIMATIC RTLS Locating Manager V2.12 or later to obtain the vendor patch. Coordinate upgrade during planned maintenance window and validate configuration import functionality post-upgrade.

Recommended fix High confidence

V2.12 or later

  1. Obtain SIMATIC RTLS Locating Manager V2.12 or later from the official Siemens download portal or cert-portal.siemens.com
  2. Backup the current configuration and database of the existing installation
  3. Stop the RTLS Locating Manager service before upgrading
  4. Install the updated version V2.12 following Siemens standard installation procedures
  5. Restart the RTLS Locating Manager service after installation
  6. Verify the application imports configuration files correctly and operates normally

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

Fix this in Simatic Rtls Locating Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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