# CVE-2024-8372: AngularJS improper sanitization in 'srcset' attribute

> Attackers can bypass image source restrictions and perform content spoofing via improper sanitization in the srcset attribute of the End-of-Life AngularJS library.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Sep 2024
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2024-8372, GHSA-m9gf-397r-hwpg, MINI-fjxv-8c87-fp6h, ROOT-APP-NPM-CVE-2024-8372, UBUNTU-CVE-2024-8372

## What is CVE-2024-8372?

CVE-2024-8372 is a medium-severity cross-site scripting vulnerability in Netapp Active Iq Unified Manager, published on 9 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 .

Weakness: CWE-1289 (Improper Validation of Unsafe Equivalence in Input)

## Which versions are affected by CVE-2024-8372?

2 open source packages ship an affected version, including angular. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `angular` | npm | From 1.3.0-rc.4 to 1.8.3 | None |
| `angular` | npm | From 1.3.0-rc.4 to 1.8.3 | None |

Products: Angularjs Angularjs, Netapp Active Iq Unified Manager.

## How do I fix CVE-2024-8372?

Product is end of life, replace it.

## Is CVE-2024-8372 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8372 exists.

## Other vulnerabilities in Netapp Active Iq Unified Manager

- [CVE-2019-10768](https://insights.sbomify.com/CVE-2019-10768/): angular Prototype Pollution vulnerability (high 7.5)
- [CVE-2019-14863](https://insights.sbomify.com/CVE-2019-14863/): AngularJS Cross-site Scripting due to failure to sanitize `xlink.href` attributes (high 7.1)
- [CVE-2020-7676](https://insights.sbomify.com/CVE-2020-7676/): Angular vulnerable to Cross-site Scripting (medium 5.4)
- [CVE-2023-26116](https://insights.sbomify.com/CVE-2023-26116/): angular vulnerable to regular expression denial of service via the angular.copy() utility (medium 5.3)
- [CVE-2023-26117](https://insights.sbomify.com/CVE-2023-26117/): angular vulnerable to regular expression denial of service via the $resource service (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8372 and fix it if it is affected.

What it is: CVE-2024-8372 is a medium-severity cross-site scripting vulnerability in Netapp Active Iq Unified Manager, published on 9 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8372 exists.

Affected packages and fixed versions:
- angular (npm): affected from 1.3.0-rc.4 up to 1.8.3; no fix listed
- angular (npm): affected from 1.3.0-rc.4 up to 1.8.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-8372/ (Markdown: https://insights.sbomify.com/CVE-2024-8372/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-8372
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-8372
- OSV: https://osv.dev/vulnerability/CVE-2024-8372

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-8372/
Summaries are generated and may contain mistakes; the official description above is the record.