CVE-2024-8373: AngularJS improper sanitization in '<source>' element

Published Sep 9, 2024
·
Updated

Improper sanitization of the value of the [srcset] attribute in <source> HTML elements 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/ContentSpoofing .

This issue affects all versions of AngularJS.

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 .

Other sources

Improper sanitization of the value of the [srcset] attribute in <source> HTML elements 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/ContentSpoofing .

This issue affects all versions of AngularJS.

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 .

— GitHub

Affected Software

9 affected componentsFixes available
npm/angular<=1.8.3
angularjs Angular.js<1.9.6
angularjs AngularJS<=1.8.3
NetApp Active Iq Unified Manager Linux
NetApp Active Iq Unified Manager Vsphere
NetApp Active Iq Unified Manager Windows
debian/angular.js<1.8.3-1+deb12u1
1.8.3-1+deb12u1
debian/angular.js<1.8.3-2
1.8.3-2
debian/angular.js
1.8.3-1+deb12u11.8.3-3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/angular.js to a version that resolves this vulnerability.

    Fixed in 1.8.3-1+deb12u1
  2. Upgrade

    Upgrade debian/angular.js to a version that resolves this vulnerability.

    Fixed in 1.8.3-2
  3. Upgrade

    Upgrade debian/angular.js to a version that resolves this vulnerability.

    Fixed in 1.8.3-1+deb12u1Fixed in 1.8.3-3

Event History

Sep 9, 2024
CVE Published
via MITRE·02:48 PM
Data Sourced
via MITRE·02:48 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:15 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via OSV·03:15 PM
DescriptionSeverityAffected Software
Advisory Published
via GitHub·03:30 PM

Peer vulnerabilities

Found alongside the following vulnerabilities.

Frequently Asked Questions

1

What is the severity of CVE-2024-8373?

CVE-2024-8373 has been classified as a significant severity vulnerability due to its potential to allow content spoofing.

2

How do I fix CVE-2024-8373?

To fix CVE-2024-8373, update to AngularJS version 1.9.6 or later, which addresses the improper sanitization issue.

3

Who is affected by CVE-2024-8373?

CVE-2024-8373 affects AngularJS versions up to 1.8.3 and versions prior to 1.9.6.

4

What type of attack can CVE-2024-8373 facilitate?

CVE-2024-8373 can facilitate content spoofing attacks by bypassing image source restrictions.

5

Can CVE-2024-8373 affect my website's security?

Yes, if you are using an affected version of AngularJS, your website could be vulnerable to content spoofing due to CVE-2024-8373.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203