Skip to content

Regular expression denial of service in scss-tokenizer

High severity GitHub Reviewed Published Jul 2, 2022 to the GitHub Advisory Database • Updated Nov 29, 2023

Package

npm scss-tokenizer (npm)

Affected versions

<= 0.4.2

Patched versions

0.4.3

Description

All versions of the package scss-tokenizer prior to 0.4.3 are vulnerable to Regular Expression Denial of Service (ReDoS) via the loadAnnotation() function, due to the usage of insecure regex.

References

Published by the National Vulnerability Database Jul 1, 2022
Published to the GitHub Advisory Database Jul 2, 2022
Reviewed Jul 6, 2022
Last updated Nov 29, 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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:N/S:U/C:N/I:N/A:H

EPSS score

0.157%
(54th percentile)

Weaknesses

CVE ID

CVE-2022-25758

GHSA ID

GHSA-7mwh-4pqv-wmr8

Source code

Credits

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