Privilege escalation via SeDebugPrivilege code injection
Published Jul 26, 2021 · Updated Aug 4, 2024
Code injection in Trezor Bridge 2.0.27 for Windows allows attackers to escalate privileges through its SeDebugPrivilege component. Public materials do not identify the code path, injected input, or operation that improperly processes that input. NVD rates the issue as remotely reachable without authentication, but the resulting privilege level and exploitation prerequisites remain undisclosed.
Summary
What happened
Code injection in Trezor Bridge 2.0.27 for Windows allows attackers to escalate privileges through its SeDebugPrivilege component. Public materials do not identify the code path, injected input, or operation that improperly processes that input. NVD rates the issue as remotely reachable without authentication, but the resulting privilege level and exploitation prerequisites remain undisclosed.
The record
- CVE
- CVE-2020-18172
- Published
- Jul 26, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-94
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 26, 2021CVE 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.
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
- GitHubAssessments proof-of-concept reportproof 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