CVE-2024-21890: NodeJS vulnerability
NodeJS · Node
Vendor fix available · Affected: NodeJS · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 61% of scored CVEs
DescriptionCVE.org
The Node.js Permission Model does not clarify in the documentation that wildcards should be only used as the last character of a file path. For example: ``` --allow-fs-read=/home/node/.ssh/*.pub ``` will ignore `pub` and give access to everything after `.ssh/`. This misleading documentation affects all users using the experimental permission model in Node.js 20 and Node.js 21. Please note that at the time this CVE was issued, the permission model 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.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- NodeJS
- Published
- February 2024
- Bounty reports
- 2 disclosed on HackerOne
Disclosed bug bounty reports about CVE-2024-21890
The reports on HackerOne that name this CVE, with HackerOne's own outcome. Titles and metadata only.
- Improper handling of wildcards in --allow-fs-read and --allow-fs-writeInternet Bug Bounty · 2024 · medium severityValid
- Improper handling of wildcards in --allow-fs-read and --allow-fs-writeNode.js · 2024 · medium severityValid
CoverageNo articles yet
No CyberSIXT article names CVE-2024-21890 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.