Unauthenticated code execution via Electron prototype pollution
Published Apr 23, 2020 · Updated Aug 4, 2024
Sandbox escape in Beaker before 0.8.9 allows remote attackers to execute code with system access through Electron internal messaging. The browser leaves Electron context isolation disabled, so prototype pollution of the internal messaging API crosses the renderer sandbox boundary. No authentication or user interaction is required; successful exploitation grants attacker-controlled code access to the host system.
Summary
What happened
Sandbox escape in Beaker before 0.8.9 allows remote attackers to execute code with system access through Electron internal messaging. The browser leaves Electron context isolation disabled, so prototype pollution of the internal messaging API crosses the renderer sandbox boundary. No authentication or user interaction is required; successful exploitation grants attacker-controlled code access to the host system.
The record
- CVE
- CVE-2020-12079
- Published
- Apr 23, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-1321, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 23, 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
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