Skip to content

express-xss-sanitizer vulnerable to Prototype Pollution via allowedTags attribute

Moderate severity GitHub Reviewed Published Sep 27, 2022 to the GitHub Advisory Database • Updated Jan 29, 2023

Package

npm express-xss-sanitizer (npm)

Affected versions

< 1.1.3

Patched versions

1.1.3

Description

The package express-xss-sanitizer before 1.1.3 is vulnerable to Prototype Pollution via the allowedTags attribute, allowing the attacker to bypass xss sanitization.

References

Published by the National Vulnerability Database Sep 26, 2022
Published to the GitHub Advisory Database Sep 27, 2022
Reviewed Sep 30, 2022
Last updated Jan 29, 2023

Severity

Moderate

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
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:N/UI:R/S:C/C:L/I:L/A:N

EPSS score

0.114%
(46th percentile)

Weaknesses

CVE ID

CVE-2022-21169

GHSA ID

GHSA-grjp-4jmr-mjcw

Source code

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