Skip to content

Missing "--allow-net" permission check for built-in Node modules

High severity GitHub Reviewed Published May 30, 2023 in denoland/deno • Updated Nov 4, 2023

Package

cargo deno (Rust)

Affected versions

= 1.34.0

Patched versions

1.34.1
cargo deno_runtime (Rust)
= 0.114.0
0.115.0

Description

Impact

Outbound HTTP requests made using the built-in "node:http" or "node:https" modules are incorrectly not checked against the network permission allow list (--allow-net). Dependencies relying on these built-in modules are subject to the vulnerability too.

Users of Deno versions prior to 1.34.0 are unaffected. Deno Deploy users are unaffected.

Patches

This problem has been patched in Deno v1.34.1 and all users are recommended to update to this version.

Workarounds

No workaround is available for this issue.

References

@bartlomieju bartlomieju published to denoland/deno May 30, 2023
Published by the National Vulnerability Database May 31, 2023
Published to the GitHub Advisory Database May 31, 2023
Reviewed May 31, 2023
Last updated Nov 4, 2023

Severity

High

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
None
Integrity
High
Availability
None

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:N/I:H/A:N

EPSS score

0.305%
(69th percentile)

Weaknesses

CVE ID

CVE-2023-33966

GHSA ID

GHSA-vc52-gwm3-8v2f

Source code

Credits

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