Skip to content

Sandbox bypass leading to arbitrary code execution in Deno

Critical severity GitHub Reviewed Published Mar 25, 2022 in denoland/deno • Updated Jun 30, 2023

Package

cargo deno (Rust)

Affected versions

>= 1.18.0, < 1.20.3

Patched versions

1.20.3

Description

Impact

The versions of Deno between release 1.18.0 and 1.20.2 (inclusive) are vulnerable to an attack where a malicious actor controlling the code executed in a Deno runtime could bypass permission checks and execute arbitrary shell code.

There is no evidence that this vulnerability has been exploited in the wild.

This vulnerability does not affect users of Deno Deploy.

Patches

The vulnerability has been patched in Deno 1.20.3.

Workarounds

There is no workaround. All users are recommended to upgrade to 1.20.3 immediately


The cause of this error was that certain FFI operations did not correctly check for permissions. The issue was fixed in this pull request.

References

@lucacasonato lucacasonato published to denoland/deno Mar 25, 2022
Published by the National Vulnerability Database Mar 25, 2022
Published to the GitHub Advisory Database Mar 29, 2022
Reviewed Mar 29, 2022
Last updated Jun 30, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

EPSS score

0.197%
(58th percentile)

CVE ID

CVE-2022-24783

GHSA ID

GHSA-838h-jqp6-cf2f

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.