Sandbox escape via nested sandbox invocation
Published Jan 24, 2020 · Updated Aug 6, 2024
Sandbox bypass in Soapbox 0.3.1 and earlier allows local users to escape imposed restrictions by launching a nested Soapbox instance. The public disclosure shows that a sandboxed process can invoke Soapbox again, but it does not identify the responsible function or validation failure. The attacker must already execute code inside a Soapbox sandbox; the nested instance grants access beyond the outer sandbox's restrictions.
Summary
What happened
Sandbox bypass in Soapbox 0.3.1 and earlier allows local users to escape imposed restrictions by launching a nested Soapbox instance. The public disclosure shows that a sandboxed process can invoke Soapbox again, but it does not identify the responsible function or validation failure. The attacker must already execute code inside a Soapbox sandbox; the nested instance grants access beyond the outer sandbox's restrictions.
The record
- CVE
- CVE-2012-6302
- Published
- Jan 24, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-269, T1548
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 24, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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
- Soapbox 0.3.1 local sandbox escape disclosureproof 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