SYSTEM code execution via weak registry permissions
Published Apr 13, 2020 · Updated Aug 4, 2024
Privilege escalation in Rockwell Automation RSLinx Classic 4.11.00 and earlier allows local users to execute code with SYSTEM privileges. Weak permissions let a low-privileged user alter an unnamed RSLinx registry key whose contents are consumed when the application opens. An authenticated local session is required, and execution occurs only when RSLinx Classic is subsequently opened under its more privileged account.
Summary
What happened
Privilege escalation in Rockwell Automation RSLinx Classic 4.11.00 and earlier allows local users to execute code with SYSTEM privileges. Weak permissions let a low-privileged user alter an unnamed RSLinx registry key whose contents are consumed when the application opens. An authenticated local session is required, and execution occurs only when RSLinx Classic is subsequently opened under its more privileged account.
The record
- CVE
- CVE-2020-10642
- Published
- Apr 13, 2020
- Updated
- Aug 4, 2024
- Vendor
- Rockwell Automation
- Product
- RSLinx Classic
- Classifications
- CWE-732, T1112, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 13, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Rockwell Automation RSLinx Classic versions 4.1.00 and prior
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo