LiveActive security incident?Get immediate response
CVE Record

CVE-2022-25758: Regular Expression Denial of Service (ReDoS)

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

MediumCVSS 5.3Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-25758 is a denial-of-service issue in scss-tokenizer. Malicious or unusually crafted SCSS annotation content can make parsing consume excessive CPU, reducing availability. It does not indicate data theft or code execution in the provided sources, but exposed parsing services or build systems may be disrupted.

Executive priority

Treat this as a moderate availability risk. It deserves normal patch-management attention, faster handling for internet-facing or multi-tenant parsing paths, and lower urgency for internal-only build tools with trusted inputs.

Technical view

The vulnerability is a Regular Expression Denial of Service in scss-tokenizer's loadAnnotation() function caused by insecure regex use. CVSS 3.1 is 5.3: network reachable, low complexity, no privileges or user interaction, with low availability impact and no confidentiality or integrity impact.

Likely exposure

Exposure is most likely in applications, developer tooling, CI pipelines, or services that use scss-tokenizer directly or through WebJars npm packaging and process untrusted SCSS or annotation content.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. The CVSS vector indicates remote, unauthenticated triggering is plausible when the vulnerable parser is reachable through attacker-controlled input, but sources do not provide confirmed exploit activity.

Researcher notes

Evidence is limited to advisory metadata and linked public references. The bundle names scss-tokenizer, loadAnnotation(), ReDoS, and CVSS details, but does not include a confirmed patched version, KEV status, CWE mapping, or active exploitation evidence.

Mitigation direction

  • Inventory direct and transitive use of scss-tokenizer, including WebJars npm packaging.
  • Check Snyk and upstream project guidance for fixed versions or recommended replacements.
  • Avoid feeding untrusted SCSS or annotation content to affected parsing paths.
  • Apply parser timeouts, input size limits, and worker isolation around SCSS processing.
  • Prioritize removal or replacement if no maintained fixed release is available.

Validation and detection

  • Search lockfiles and SBOMs for scss-tokenizer and org.webjars.npm packaging.
  • Map where SCSS parsing accepts user, tenant, repository, or CI-supplied content.
  • Run dependency scanners that include CVE-2022-25758 or the linked Snyk advisories.
  • Review production safeguards for CPU limits, request timeouts, and job cancellation.
  • Confirm whether the vulnerable loadAnnotation() path is reachable in your deployment.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-25758 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2022-25758Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/ascss-tokenizer0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.