Node: Improperly Controlled Modification of Object Prototype Attributes
CVE-2022-21824 is a high-severity improperly controlled modification of object prototype attributes vulnerability in Node from Node.js, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 4.*, 5.*, 6.* as the first without the flaw, so updating Node to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 21.5% chance of exploitation within 30 days, which is in the top 2.34% of all scored CVEs.
EPSS places it among the vulnerabilities most likely to be exploited soon.
What to do
- Update Node to 4.* or 5.* or 6.* or 7.*, whichever matches your release line, or a later version.
- Update Node.js to 12.22.9 or 14.18.3 or 16.13.2 or 17.3.1, whichever matches your release line, or a later version.
- Read the advisory on nodejs.org for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Node.js | Node | 4.0 up to, but not including, 4.*; 5.0 up to, but not including, 5.*; 6.0 up to, but not including, 6.*; 7.0 up to, but not including, 7.*; 8.0 up to, but not including, 8.*; 9.0 up to, but not including, 9.*; 10.0 up to, but not including, 10.*; 11.0 up to, but not including, 11.*; and 6 more ranges | 4.*, 5.*, 6.*, 7.*, 8.*, 9.* |
| Node.js | Node.js | 12.0.0 up to, but not including, 12.22.9; 14.0.0 up to, but not including, 14.18.3; 16.0.0 up to, but not including, 16.13.2; 17.0.0 up to, but not including, 17.3.1 | 12.22.9, 14.18.3, 16.13.2, 17.3.1 |
| Oracle | MySQL Cluster | 8.0.29 and earlier | Not stated |
| Oracle | MySQL Connectors | 8.0.28 and earlier | Not stated |
| Oracle | MySQL Enterprise Monitor | 8.0.29 and earlier | Not stated |
| Oracle | MySQL Server | 8.0.29 and earlier | Not stated |
| Oracle | MySQL Workbench | 8.0.28 and earlier | Not stated |
| Oracle | Peoplesoft Enterprise Peopletools | 8.58; 8.59 | Not stated |
| Debian | Debian Linux | 10.0; 11.0 | Not stated |
| NetApp | Oncommand Insight | Not specified in the record | Not stated |
| NetApp | Oncommand Workflow Automation | Not specified in the record | Not stated |
| NetApp | Snapcenter | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- LowLimited modification of data is possible.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.2 | High | NVD |
| CVSS 2.0 | 6.4 | Medium | NVD |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improperly Controlled Modification of Object Prototype Attributes
The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.
How developers prevent this class of flaw
- By freezing the object prototype first (for example, Object.freeze(Object.prototype)), modification of the prototype becomes impossible.
- By blocking modifications of attributes that resolve to object prototype, such as proto or prototype, this weakness can be mitigated.
- When handling untrusted objects, validating using a schema can be used.
More Improperly Controlled Modification of Object Prototype Attributes vulnerabilities (CWE-1321)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Advisories
Patches and release notes
- hackerone.com/reports/1431042Issue Tracking, Mitigation, Third Party Advisory
- oracle.com/security-alerts/cpuapr2022.htmlThird Party Advisory
Third-party and government advisories
- lists.debian.org/debian-lts-announce/2022/10/msg00006.htmlMailing List, Third Party Advisory
- security.netapp.com/advisory/ntap-20220325-0007/Third Party Advisory
- security.netapp.com/advisory/ntap-20220729-0004/Third Party Advisory
- debian.org/security/2022/dsa-5170Third Party Advisory
- oracle.com/security-alerts/cpujul2022.htmlThird Party Advisory
Other vulnerabilities in Node
- 7.5 High severity
- 7.5 High severity
- 8.1 High severity
- 7.5 High severity
- 7.5 High severity
- 8.1 High severity
Recent Improperly Controlled Modification of Object Prototype Attributes vulnerabilities
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.