Sandbox bypass via unchecked nested static imports
Published May 28, 2021 · Updated Aug 3, 2024
Improper privilege management in Deno 1.5.0 through 1.10.1 allows attackers to read local or network data via nested static imports. During import() and new Worker module loading, Deno checks the dynamic module but omits equivalent network or file-system checks for its static dependencies. Attackers must control a module in the program graph; 1.7.0 through 1.10.1 require no Deno permissions, while 1.5.x and 1.6.x require permission to load the module.
Summary
What happened
Improper privilege management in Deno 1.5.0 through 1.10.1 allows attackers to read local or network data via nested static imports. During import() and new Worker module loading, Deno checks the dynamic module but omits equivalent network or file-system checks for its static dependencies. Attackers must control a module in the program graph; 1.7.0 through 1.10.1 require no Deno permissions, while 1.5.x and 1.6.x require permission to load the module.
The record
- CVE
- CVE-2021-32619
- Published
- May 28, 2021
- Updated
- Aug 3, 2024
- Vendor
- Deno Land Inc.
- Product
- Deno
- Classifications
- CWE-269, T1083, T1005
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 28, 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=< 1.10.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