CVE-2024-8372

What it actually does

Improper sanitization of the srcset attribute value allows bypassing image source restrictions, enabling content spoofing in affected AngularJS applications.

Why it matters to the business

Attackers can inject misleading or malicious content into web applications, eroding user trust and potentially facilitating phishing or misinformation without requiring updates due to end-of-life status.

How an attack unfolds

An attacker identifies a vulnerable AngularJS application and supplies a crafted srcset attribute value that evades sanitization checks, resulting in the display of unauthorized content sources.

How to fix it

Migrate away from AngularJS to a supported framework such as Angular as the project is end-of-life and receives no patches.

How to confirm the fix worked

Audit application dependencies for AngularJS versions 1.3.0-rc.4 or later and review code handling srcset attributes for sanitization logic.

Typical attack path

1. Identify web application using vulnerable AngularJS version
2. Craft malicious srcset attribute payload
3. Inject payload into input that populates srcset
4. Trigger rendering to bypass restrictions and spoof content

How to detect it

Review web application logs for unusual srcset attribute values or unexpected image sources; inspect client-side code for attribute handling.

What your security team should do

• Prioritize migration from AngularJS due to lack of support
• Implement additional input sanitization layers if migration is delayed
• Monitor for content spoofing attempts in application logs