CVE-2023-28444 Details
Description
angular-server-side-configuration helps configure an angular application at runtime on the server or in a docker container via environment variables. 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.0.0 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. This vulnerability has been mitigated in version 15.1.0, by adding an option `searchPattern` which restricts the detection file range by default. As a workaround, manually edit or create ngssc.json or run script after ngssc.json generation.
A critical information disclosure vulnerability has been identified in the 'angular-server-side-configuration' package, specifically in versions 15.0.0 prior to 15.1.0. This vulnerability arises from the package's environment variable detection feature, which, in version 15.0.0, was expanded to search the entire project workspace. In a monorepo setup that includes a Node.js backend, this could result in unintended exposure of environment variables meant for the backend, by writing them to an 'ngssc.json' file. During deployment, these variables could be populated into the application's 'index.html' file, thereby exposing sensitive information. However, this vulnerability does not impact standard Angular projects without a backend component.
Users can update to 'angular-server-side-configuration' version 15.1.0, which addresses this vulnerability by restricting the default search pattern for environment variables to the project's 'sourceRoot', excluding files with 'server' in the name. Alternatively, users can manually edit or create the 'ngssc.json' file or run a script after 'ngssc.json' generation to manage environment variable exposure.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Feb 24, 2025References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-200 | Exposure of Sensitive Information to an Unauthorized Actor | [email protected] |
| CWE-200 | Exposure of Sensitive Information to an Unauthorized Actor | [email protected] |
| CWE-538 | Insertion of Sensitive Information into Externally-Accessible File or Directory | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| angular-server-side-configuration project angular-server-side-configuration | >= 15.0.0, < 15.1.0 |
CPE
Remediation
| |
Change History
6 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Nov 21, 2024 | CVE Modified | CVE |
| May 14, 2024 | CVE Modified | [email protected] |
| Nov 7, 2023 | CVE Modified | [email protected] |
| Apr 3, 2023 | Initial Analysis | [email protected] |