dbcve.org
Simatic Rtls Locating ManagerApplication · Siemens

CVE-2020-10053

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 writes sensitive data, such as database credentials in configuration files. A local attacker with access to the configuration files could use this information to launch further attacks.

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

SIMATIC RTLS Locating Manager versions prior to V2.12 store sensitive data, including database credentials, in plaintext within configuration files. A local attacker with file system access to these configuration files can read the stored credentials and use them to compromise connected databases or escalate privileges.

MitigationUpgrade to SIMATIC RTLS Locating Manager V2.12 or later, which addresses the improper credential storage. If immediate upgrade is not feasible, audit configuration file permissions to restrict local access and rotate compromised credentials.

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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. Confirm SIMATIC RTLS Locating Manager is installed
    Check for the presence of the Siemens Simatic RTLS Locating Manager software on the system, typically found in Program Files or a dedicated installation directory. Look for executable files or service entries named 'RTLS Locating Manager' or similar variants.
    Affected if The software is present on the system
  2. Identify the installed version
    Locate the version information for the installed RTLS Locating Manager. Check the executable properties (right-click the main .exe file, view Details/Version tab), or look for a version file in the installation directory. Alternatively, check the Windows Programs and Features list for the installed version number.
    Affected if The installed version is below V2.12 (e.g., V2.10, V2.11, or any version prior to 2.12)
  3. Locate configuration files
    Search the installation directory for configuration files with extensions such as .xml, .ini, .cfg, .conf, .config, or .properties. Common naming patterns include files containing 'config', 'settings', 'db', 'database', 'connection', or 'credential' in the filename.
    Affected if Configuration files exist in the installation directory
  4. Inspect configuration files for plaintext credentials
    Open each configuration file found in a text editor and search for patterns indicating stored credentials, such as keywords like 'password', 'pwd', 'user', 'uid', 'connectionstring', 'dbpassword', or values that appear to be passwords. Check if any sensitive values are stored in cleartext rather than encrypted, hashed, or masked.
    Affected if Database credentials, connection strings, or other sensitive authentication data are stored in plaintext (readable, unencrypted format) within any configuration file

A system is affected by this CVE if SIMATIC RTLS Locating Manager is installed with a version prior to V2.12 AND configuration files contain unencrypted (plaintext) database credentials or sensitive authentication strings.

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, which addresses the improper credential storage. If immediate upgrade is not feasible, audit configuration file permissions to restrict local access and rotate compromised credentials.

Recommended fix High confidence

V2.12

  1. Back up the current SIMATIC RTLS Locating Manager installation and configuration files
  2. Download SIMATIC RTLS Locating Manager version V2.12 or higher from the Siemens cert-portal or official Siemens support channels
  3. Install the updated version following Siemens installation documentation
  4. Verify that configuration files no longer contain plaintext sensitive data such as database credentials
  5. Confirm the application functions normally after upgrade

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

Fix this in Simatic Rtls Locating Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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