GHSA-r3hf-q8q7-fv2p: @nguniversal/common Cross-Site Scripting Vulnerability

HIGH
Share
CWE-79
Published
Advisory Summary

GHSA-r3hf-q8q7-fv2p is a HIGH cross-site scripting vulnerability (CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) affecting @nguniversal/common libraries in the npm ecosystem. The issue involves angular critical css inlining cross-site scripting vulnerability advisory. Remediation is available by upgrading affected packages to version 16.1.2.

GHSA-r3hf-q8q7-fv2p at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-r3hf-q8q7-fv2p
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Affected Product @nguniversal/common
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-r3hf-q8q7-fv2p

To remediate this vulnerability, upgrade all affected @nguniversal/common dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@nguniversal/common fixed: 16.1.2 
npm install @nguniversal/common@16.1.2
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

npm ls @nguniversal/common

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-r3hf-q8q7-fv2p, inspect your project dependencies using npm:

npm ls @nguniversal/common

Analyze the terminal output to locate any version of @nguniversal/common in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 16.1.2), your application is affected.

Note: The npm ls @nguniversal/common command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'), where the product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. In @nguniversal/common, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact Angular Universal applications on 16.1.0 and 16.1.1 using critical CSS inlining are vulnerable to a [cross-site scripting (XSS)](https://owasp.org/www-community/attacks/xss/) attack where an attacker can trick another user into visiting a page which injects malicious JavaScript. Angular CLI applications without Universal do perform critical CSS inlining as well, however exploiting this requires a malicious actor to already have access to modify source code directly. ### Patches `@nguniversal/common` should be upgraded to 16.1.2 or higher. 16.2.0-rc.0 is safe. ### Workarounds The easiest solution is likely to upgrade Universal to 16.1.2 or downgrade to 16.0.x or lower. Alternatively you can [override](https://docs.npmjs.com/cli/v9/configuring-npm/package-json#overrides) specifically the `critters` dependency with version `0.0.20` in your `package.json`. ```json { "overrides": { "critters": "0.0.20" } } ``` ### References * [Angular Blog Post](https://blog.angular.io/notice-of-xss-issue-affecting-angular-universal-16-1-0-16-1-1-95dbae068f)

GHSA-r3hf-q8q7-fv2p Affected @nguniversal/common Versions

1 component(s)
Fixed Versions:
16.1.2
Product / Package Ecosystem Affected Versions Fixed Version
@nguniversal/common
npm/@nguniversal/common
npm
≥ 16.1.0
< 16.1.2
16.1.2

References

GitHub Advisory / Wiki ADVISORY
https://github.com/angular/universal/security/advisories/GHSA-r3hf-q8q7-fv2p
@nguniversal/common Source Repository REPOSITORY
https://github.com/angular/universal

Frequently Asked Questions

What is GHSA-r3hf-q8q7-fv2p?
GHSA-r3hf-q8q7-fv2p is a security vulnerability in @nguniversal/common involving Angular critical CSS inlining Cross-site Scripting Vulnerability Advisory under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting').
Which @nguniversal/common versions are affected?
Affected versions include releases prior to 16.1.2 across affected packages: @nguniversal/common.
What version fixes GHSA-r3hf-q8q7-fv2p?
Upgrading to 16.1.2 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @nguniversal/common affected?
Yes, @nguniversal/common is affected in releases prior to 16.1.2. Upgrade your dependency to 16.1.2 or later.
What CWE is associated with GHSA-r3hf-q8q7-fv2p?
GHSA-r3hf-q8q7-fv2p is classified under CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') (The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.).
How can I check npm dependencies for GHSA-r3hf-q8q7-fv2p?
Run the dependency tree command: 'npm ls @nguniversal/common'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-r3hf-q8q7-fv2p",
  "modified" : "2023-08-09T12:51:51Z",
  "published" : "2023-08-09T12:51:51Z",
  "aliases" : [ ],
  "summary" : "Angular critical CSS inlining Cross-site Scripting Vulnerability Advisory",
  "details" : "### Impact\nAngular Universal applications on 16.1.0 and 16.1.1 using critical CSS inlining are vulnerable to a [cross-site scripting (XSS)](https://owasp.org/www-community/attacks/xss/) attack where an attacker can trick another user into visiting a page which injects malicious JavaScript.\n\nAngular CLI applications without Universal do perform critical CSS inlining as well, however exploiting this requires a malicious actor to already have access to modify source code directly.\n\n### Patches\n`@nguniversal/common` should be upgraded to 16.1.2 or higher. 16.2.0-rc.0 is safe.\n\n### Workarounds\nThe easiest solution is likely to upgrade Universal to 16.1.2 or downgrade to 16.0.x or lower. Alternatively you can [override](https://docs.npmjs.com/cli/v9/configuring-npm/package-json#overrides) specifically the `critters` dependency with version `0.0.20` in your `package.json`.\n\n```json\n{\n  \"overrides\": {\n    \"critters\": \"0.0.20\"\n  }\n}\n```\n\n### References\n\n* [Angular Blog Post](https://blog.angular.io/notice-of-xss-issue-affecting-angular-universal-16-1-0-16-1-1-95dbae068f)",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@nguniversal/common"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "16.1.0"
      }, {
        "fixed" : "16.1.2"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/angular/universal/security/advisories/GHSA-r3hf-q8q7-fv2p"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/angular/universal"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-79" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2023-08-09T12:51:51Z",
    "nvd_published_at" : null
  }
}