CVE-2022-21824Not scoredCWE-471

CVE-2022-21824: NodeJS vulnerability

NodeJS · Node

Vendor fix available · Affected: NodeJS · Exploitation: likely to be exploited (10% or more)

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

21.5%probability of exploitation in the next 30 days

97th percentile

050100

Higher than 97% of scored CVEs

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

DescriptionCVE.org

Due to the formatting logic of the "console.table()" function it was not safe to allow user controlled input to be passed to the "properties" parameter while simultaneously passing a plain object with at least one property as the first parameter, which could be "__proto__". The prototype pollution has very limited control, in that it only allows an empty string to be assigned to numerical keys of the object prototype.Node.js >= 12.22.9, >= 14.18.3, >= 16.13.2, and >= 17.3.1 use a null protoype for the object these properties are being assigned to.

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 8 more

On the Atlas

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

Open the Atlas

Exploitation: Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Modification of Assumed-Immutable Data (MAID) · Other weaknesses
Vendor: NodeJS
Published: February 2022
Band: Likely to be exploited (10% or more), February 2022
Bounty reports: 1 disclosed on HackerOne

Disclosed bug bounty reports about CVE-2022-21824

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

Prototype pollution via console.table propertiesNode.js · 2022 · low severityValid

CoverageNo articles yet

No CyberSIXT article names CVE-2022-21824 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.