CVE-2020-10051
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 · uneditedA vulnerability has been identified in SIMATIC RTLS Locating Manager (All versions < V2.10.2). Multiple services of the affected application are executed with SYSTEM privileges while the call path is not quoted. This could allow a local attacker to inject arbitrary commands that are execeuted instead of the legitimate 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 · high confidenceSIMATIC RTLS Locating Manager versions before V2.10.2 have an unquoted service path vulnerability. Multiple Windows services run with SYSTEM privileges but the executable paths contain spaces and are not enclosed in quotes, allowing Windows to misinterpret path components and execute attacker-placed binaries instead of the intended service.
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< 2.10.2CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Check if SIMATIC RTLS Locating Manager is installedLook for SIMATIC RTLS Locating Manager in the Windows installed programs list via Control Panel > Programs and Features, or query the registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for entries containing 'SIMATIC RTLS' or 'Locating Manager'Affected if The software is found installed on the system
-
Identify the installed versionLocate the SIMATIC RTLS Locating Manager installation directory and check the version information in the executable properties, or query the registry for the version value under the product's uninstall entryAffected if The version is lower than 2.10.2 or the version cannot be determined
-
Enumerate Windows services related to SIMATIC RTLSOpen Services.msc or run 'sc query' and filter for services with names containing 'SIMATIC', 'RTLS', or 'Locating', then run 'sc qc <service_name>' for each to retrieve the binary pathAffected if Services associated with SIMATIC RTLS Locating Manager are found on the system
-
Inspect service executable paths for unquoted spacesFor each identified service, examine the BINPATH in the service configuration (via 'sc qc' or registry at HKLM\SYSTEM\CurrentControlSet\Services\<service_name>). Check if the path contains spaces and is not enclosed in double quotesAffected if The executable path contains spaces and is NOT surrounded by double quotes (e.g., C:\Program Files\Siemens\simatic.exe instead of "C:\Program Files\Siemens\simatic.exe")
-
Verify service privilege levelRun 'sc qc <service_name>' and check the START_TYPE and look at the service properties in Services.msc or run 'sc queryex' to confirm the service runs under the LocalSystem accountAffected if The service with the unquoted path runs under the LocalSystem or SYSTEM account
The system is affected if SIMATIC RTLS Locating Manager version is below 2.10.2 and any of its Windows services have unquoted executable paths containing spaces while running with SYSTEM privileges.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data2.10.2
Upgrade to SIMATIC RTLS Locating Manager V2.10.2 or later, which includes the patch for proper path quoting. Alternatively, verify that all service executable paths in the Windows registry are fully quoted if patching is not immediately feasible.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10051 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-10051 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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