Root escalation via writable privileged configuration
Published Mar 15, 2020 · Updated Aug 4, 2024
Privilege escalation in v2rayL 2.1.3 allows local users to gain root access by modifying a service configuration file. The low-privileged account owns /etc/v2rayL/config.json, whose attacker-controlled commands v2rayL.service executes as root. Exploitation requires local access and permission to restart v2rayL.service through Sudo, after which arbitrary commands run with root privileges.
Summary
What happened
Privilege escalation in v2rayL 2.1.3 allows local users to gain root access by modifying a service configuration file. The low-privileged account owns /etc/v2rayL/config.json, whose attacker-controlled commands v2rayL.service executes as root. Exploitation requires local access and permission to restart v2rayL.service through Sudo, after which arbitrary commands run with root privileges.
The record
- CVE
- CVE-2020-10589
- Published
- Mar 15, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-269, T1548.003
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 15, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
- v2rayL local privilege-escalation exploit scriptproof of concept · unverified
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