SYSTEM code execution via writable service binary
Published Jun 16, 2020 · Updated Aug 4, 2024
Local privilege escalation in I2P 0.7.5 through 0.9.45 for Windows allows local users to execute code with SYSTEM privileges. The installer grants BUILTIN\Users full control over C:\Program Files\i2p, allowing I2PSvc.exe to be replaced before the service starts. An unprivileged local account and the optional I2PSvc service installation are required; the replacement binary runs as SYSTEM at operating-system startup.
Summary
What happened
Local privilege escalation in I2P 0.7.5 through 0.9.45 for Windows allows local users to execute code with SYSTEM privileges. The installer grants BUILTIN\Users full control over C:\Program Files\i2p, allowing I2PSvc.exe to be replaced before the service starts. An unprivileged local account and the optional I2PSvc service installation are required; the replacement binary runs as SYSTEM at operating-system startup.
The record
- CVE
- CVE-2020-13431
- Published
- Jun 16, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-732, T1574.010
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 16, 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
- I2P Windows local privilege escalation proof of conceptproof of concept · demonstrated
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