GHSA-gwvm-vrp4-4pp5
CRITICALGHSA-gwvm-vrp4-4pp5 is a critical-severity (CVSS 9.9) Information Exposure vulnerability in angular-server-side-configuration. O3 Security confirms whether GHSA-gwvm-vrp4-4pp5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
angular-server-side-configuration information disclosure vulnerability in monorepo with node.js backend
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
angular-server-side-configurationnpmDescription
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.
# Update via npm
npm update angular-server-side-configuration
## Or more specific
npm install [email protected]
# Update via pnpm
pnpm update angular-server-side-configuration
## Or more specific
pnpm add [email protected]
# Update via yarn
yarn update angular-server-side-configuration
## Or more specific
yarn add [email protected]
Workarounds
Manually edit or create ngssc.json or run a script after ngssc.json generation
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | angular-server-side-configuration | ≥ 15.0.0&&< 15.1.0 | 15.1.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for angular-server-side-configuration. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update angular-server-side-configuration to 15.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gwvm-vrp4-4pp5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-gwvm-vrp4-4pp5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-gwvm-vrp4-4pp5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-gwvm-vrp4-4pp5 in your dependencies?
O3 detects GHSA-gwvm-vrp4-4pp5 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.