Skip to content
Sign in
CVE-2023-38552Not scoredCWE-345

CVE-2023-38552: NodeJS vulnerability

NodeJS · Node

Vendor fix available · Affected: NodeJS · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

1.2%probability of exploitation in the next 30 days
69th percentile
050100

Higher than 69% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

When the Node.js policy feature checks the integrity of a resource against a trusted manifest, the application can intercept the operation and return a forged checksum to the node's policy implementation, thus effectively disabling the integrity check. Impacts: This vulnerability affects all users using the experimental policy mechanism in all active release lines: 18.x and, 20.x. Please note that at the time this CVE was issued, the policy mechanism is an experimental feature of Node.js.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • NodeJS · Nodefrom 4.0 before 4.*; from 5.0 before 5.*; from 6.0 before 6.*; from 7.0 before 7.*; from 8.0 before 8.*; from 9.0 before 9.* and 11 more

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
NodeJS
Published
October 2023

Disclosed bug bounty reports about CVE-2023-38552

The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.

CoverageNo articles yet

No CyberSIXT article names CVE-2023-38552 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

Updated AboutDevelopersSign in