Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

@nguniversal/common

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. UnratednpmAmendedPublished

    Angular critical CSS inlining Cross-site Scripting Vulnerability Advisory

    GHSA-r3hf-q8q7-fv2p

    Affected
    • npm @nguniversal/common >= 16.1.0, < 16.1.2
    Fixed in
    16.1.2· Vendor fix available
    Issue
    Impact Angular Universal applications on 16.1.0 and 16.1.1 using critical CSS inlining are vulnerable to a cross-site scripting (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 specifically the critters dependency with version 0.0.20 in your package.json. References Angular Blog Post

    Recommended action: Upgrade to 16.1.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →