angular: Insertion of Sensitive Information Into Sent Data
CVE-2025-66035 is a high-severity insertion of sensitive information into sent data vulnerability in angular, with a CVSS 4.0 base score of 7.7 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected angular versions: >= 21.0.0-next.0, < 21.0.1; >= 20.0.0-next.0, < 20.3.14; < 19.2.16. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.72% chance of exploitation within 30 days, higher than 54% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update RUGGEDCOM RST2428P to V4.0 or a later version.
- Update SIDIS Prime to V4.0.800 or a later version.
- Read the advisory on github.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Angular | angular | >= 21.0.0-next.0, < 21.0.1; >= 20.0.0-next.0, < 20.3.14; < 19.2.16 | Not stated |
| Siemens | RUGGEDCOM RST2428P | before V4.0 | V4.0 |
| Siemens | SIDIS Prime | before V4.0.800 | V4.0.800 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Attack requirements
- NoneThe attack does not depend on a particular deployment or configuration.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Confidentiality (vulnerable system)
- NoneNo loss of confidentiality on the vulnerable system.
- Integrity (vulnerable system)
- NoneNo loss of integrity on the vulnerable system.
- Availability (vulnerable system)
- NoneNo loss of availability on the vulnerable system.
- Confidentiality (other systems)
- HighSerious loss of confidentiality on systems beyond the vulnerable one.
- Integrity (other systems)
- NoneNo loss of integrity on systems beyond the vulnerable one.
- Availability (other systems)
- NoneNo loss of availability on systems beyond the vulnerable one.
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. Scored by CNA (github.com).
Official description
Angular is a development platform for building mobile and desktop web applications using TypeScript/JavaScript and other languages. Prior to versions 19.2.16, 20.3.14, and 21.0.1, there is a XSRF token leakage via protocol-relative URLs in angular HTTP clients. The vulnerability is a Credential Leak by App Logic that leads to the unauthorized disclosure of the Cross-Site Request Forgery (XSRF) token to an attacker-controlled domain. Angular's HttpClient has a built-in XSRF protection mechanism that works by checking if a request URL starts with a protocol (http:// or https://) to determine if it is cross-origin. If the URL starts with protocol-relative URL (//), it is incorrectly treated as a same-origin request, and the XSRF token is automatically added to the X-XSRF-TOKEN header. This issue has been patched in versions 19.2.16, 20.3.14, and 21.0.1. A workaround for this issue involves avoiding using protocol-relative URLs (URLs starting with //) in HttpClient requests. All backend communication URLs should be hardcoded as relative paths (starting with a single /) or fully qualified, trusted absolute URLs.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Insertion of Sensitive Information Into Sent Data
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
How developers prevent this class of flaw
- Specify which data in the software should be regarded as sensitive. Consider which types of users should have access to which types of data.
- Ensure that any possibly sensitive data specified in the requirements is verified with designers to ensure that it is either a calculated risk or mitigated elsewhere. Any information that is not necessary to the functionality should be removed in order to lower both the overhead and the possibility of security sensitive data being sent.
- Setup default error messages so that unexpected errors do not disclose sensitive information.
More Insertion of Sensitive Information Into Sent Data vulnerabilities (CWE-201)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
- github.com/angular/angular/commit/0276479e7d0e280e0f8d26fa567d3b7aa97a516f
- github.com/angular/angular/commit/05fe6686a97fa0bcd3cf157805b3612033f975bc
- github.com/angular/angular/commit/3240d856d942727372a705252f7c8c115394a41e
- github.com/angular/angular/releases/tag/19.2.16
- github.com/angular/angular/releases/tag/20.3.14
- github.com/angular/angular/releases/tag/21.0.1
Other references
Other vulnerabilities in angular
- 8.2 High severity
- 8.2 High severity
- 8.2 High severity
- 8.7 High severity
- 9.1 Critical severity
- 7.5 High severity
Recent Insertion of Sensitive Information Into Sent Data vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.7 High severity
- 7.5 High severity
- 7.7 High severity
Spotted an error? Tell us.