Skip to content

← Public intelligence

npm package

angular-server-side-configuration

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. Critical, CVSS 9.9npmAmendedPublished

    angular-server-side-configuration information disclosure vulnerability in monorepo with node.js backend

    CVE-2023-28444 · GHSA-gwvm-vrp4-4pp5

    Affected
    • npm angular-server-side-configuration >= 15.0.0, < 15.1.0
    Fixed in
    15.1.0· Vendor fix available
    Issue
    Impact angular-server-side-configuration detects used environment variables in TypeScript (.ts) files during build time of an Angular CLI project. The detected environment variables are written to a ngssc.json file in the output directory. During deployment of an Angular based app, the environment variables based on the variables from ngssc.json are inserted into the apps index.html (or defined index file). With version 15 the environment variable detection was widened to the entire project, relative to the angular.json file from the Angular CLI. In a monorepo setup, this could lead to environment variables intended for a backend/service to be detected and written to the ngssc.json, which would then be populated and exposed via index.html. This has NO IMPACT, in a plain Angular project that has no backend component. Patches Vulnerability has been mitigated in 15.1.0, by adding an option searchPattern which restricts the detection file range by default. Workarounds Manually edit or…

    Recommended action: Upgrade to 15.1.0 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 →