AngularJS improper sanitization in 'srcset' attribute
Not confirmed exploited. 1 of 8 rule sources name it.
Improper sanitization of the value of the 'srcset' attribute in AngularJS allows attackers to bypass common image source restrictions, which can also lead to a form of Content Spoofing… More
Improper sanitization of the value of the 'srcset' attribute in AngularJS allows attackers to bypass common image source restrictions, which can also lead to a form of Content Spoofing https://owasp.org/www-community/attacks/Content_Spoofing . This issue affects AngularJS versions 1.3.0-rc.4 and greater. Note: The AngularJS project is End-of-Life and will not receive any updates to address this issue. For more information see here https://docs.angularjs.org/misc/version-support-status .
Edge coverage
Claimed by vendorsAsk Vigil
AI · answers from this pageWorkers AI (Llama 3.3). Can be wrong: check the cited source.
Severity, decoded
CVSS 3.1Exploitable over the network under specific conditions, with no privileges and no user interaction, leading to low impact on integrity and availability.
How the score is built
- Attack vectorAn attacker can reach it over the internet; no access to your network needed.Network
- Attack complexityThe attack only works when conditions outside the attacker's control line up.High
- Privileges requiredNo account or login is needed.None
- User interactionNo one has to click or open anything; the attack works on its own.None
- ScopeThe damage stays within the vulnerable component.Unchanged
- Confidentiality impactNo data is exposed.None
- Integrity impactAn attacker can change some data, but with limited control or limited effect.Low
- Availability impactAn attacker can slow the component down or interrupt it now and then.Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:LPublic exploit code or a detailed write-up exists, but CISA has not seen attacks.
At least one step needs hands-on work, which slows mass attacks.
A successful attack gives limited control over the affected software or limited access to its data.
Public exploits
None foundNo exploit in Exploit-DB or Metasploit, and no scanner template. That lowers, but doesn't remove, the chance of mass exploitation.
Timeline
- 2024-09-09CVE publishedCVE List
- 2025-04-28F5 ships a ruleAngular.js attribute ng-Srcset (Parameter)
Vendor statements
QuotedCloudflareWAF Managed Rules
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
AWSAWS WAF Managed Rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.
Microsoft AzureFront Door and Application Gateway WAF (DRS)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.
Google CloudCloud Armor preconfigured WAF rules
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Google names few CVEs: the release notes start in May 2024 and the rules reference lists CVEs without dates. Its cve-canary rules are opt-in.
FastlyNext-Gen WAF virtual patches
The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.
F5Attack signatures (Distributed Cloud WAF)
First rule 2025-04-28, 231 days after the CVE was published.
Added: signature 200101909 "Angular.js attribute ng-Srcset (Parameter)" (Cross Site Scripting (XSS), risk High), systems: System Independent, AngularJS. References: CVE-2024-8372.
Added: signature 200101910 "Angular.js attribute ng-Srcset (Header)" (Cross Site Scripting (XSS), risk High), systems: System Independent, AngularJS. References: CVE-2024-8372.
Added: signature 200101911 "Angular.js attribute ng-Srcset (URI)" (Cross Site Scripting (XSS), risk High), systems: System Independent, AngularJS. References: CVE-2024-8372.
Added: signature 200101912 "Angular.js attribute ng-Attr-Srcset (Parameter)" (Cross Site Scripting (XSS), risk High), systems: System Independent, AngularJS. References: CVE-2024-8372.
Added: signature 200101913 "Angular.js attribute ng-Attr-Srcset (Header)" (Cross Site Scripting (XSS), risk High), systems: System Independent, AngularJS. References: CVE-2024-8372.
Added: signature 200101914 "Angular.js attribute ng-Attr-Srcset (URI)" (Cross Site Scripting (XSS), risk High), systems: System Independent, AngularJS. References: CVE-2024-8372.
Added: signature 200101915 "Angular.js attribute ng-Prop-Srcset (Parameter)" (Cross Site Scripting (XSS), risk High), systems: System Independent, AngularJS. References: CVE-2024-8372.
Added: signature 200101916 "Angular.js attribute ng-Prop-Srcset (Header)" (Cross Site Scripting (XSS), risk High), systems: System Independent, AngularJS. References: CVE-2024-8372.
Added: signature 200101917 "Angular.js attribute ng-Prop-Srcset (URI)" (Cross Site Scripting (XSS), risk High), systems: System Independent, AngularJS. References: CVE-2024-8372.
AkamaiApp & API Protector (Adaptive Security Engine)
This vendor publishes no machine-readable rule changelog we can check.
OWASP CRSCore Rule Set (open source, used inside many WAFs)
We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. CRS rarely names CVEs: it relies on generic detections. Our own lab measures what it actually blocks.
Social
No posts seen yet on X, Bluesky, Mastodon, Hacker News or GitHub.