Sandbox escape via unconstrained module resolution
Published Jul 19, 2021 · Updated Aug 3, 2024
Sandbox escape in Racket before 8.2 allows attackers to control system functions via crafted modules supplied to an evaluator. The sandbox module resolver accepted reader and require paths from evaluated code without constraining syntactic module references, so system modules resolved attacker-created modules instead of intended dependencies. Reachability requires an application that evaluates attacker-supplied Racket code in-process; exploitation grants facilities that the sandbox intended to restrict.
Summary
What happened
Sandbox escape in Racket before 8.2 allows attackers to control system functions via crafted modules supplied to an evaluator. The sandbox module resolver accepted reader and require paths from evaluated code without constraining syntactic module references, so system modules resolved attacker-created modules instead of intended dependencies. Reachability requires an application that evaluates attacker-supplied Racket code in-process; exploitation grants facilities that the sandbox intended to restrict.
The record
- CVE
- CVE-2021-32773
- Published
- Jul 19, 2021
- Updated
- Aug 3, 2024
- Vendor
- Racket
- Product
- Racket
- Classifications
- CWE-610, CWE-441
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 19, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 8.2
What conditions does exploitation require?
What is affected?
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
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