Skip to content

Prototype Pollution in Node-Red

High severity GitHub Reviewed Published Feb 19, 2021 in node-red/node-red • Updated Feb 1, 2023

Package

npm @node-red/runtime (npm)

Affected versions

< 1.2.8

Patched versions

1.2.8

Description

Impact

Node-RED 1.2.7 and earlier contains a Prototype Pollution vulnerability in the admin API. A badly formed request can modify the prototype of the default JavaScript Object with the potential to affect the default behaviour of the Node-RED runtime.

Patches

The vulnerability is patched in the 1.2.8 release.

Workarounds

A workaround is to ensure only authorised users are able to access the editor url.

For more information

If you have any questions or comments about this advisory:

Acknowledgements

Thanks to the Tencent Woodpecker Security Team for disclosing this vulnerability.

References

@knolleary knolleary published to node-red/node-red Feb 19, 2021
Reviewed Feb 26, 2021
Published to the GitHub Advisory Database Feb 26, 2021
Published by the National Vulnerability Database Feb 26, 2021
Last updated Feb 1, 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
Low
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:L/UI:N/S:C/C:N/I:H/A:N

EPSS score

0.079%
(36th percentile)

Weaknesses

CVE ID

CVE-2021-21297

GHSA ID

GHSA-xp9c-82x8-7f67

Source code

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