Skip to content

GHSA-m9gf-397r-hwpg CVE-2024-8372

AngularJS allows attackers to bypass common image source restrictions

Medium npm
Severity
0.0 / 10
Medium · CVSS 4.0
Exploit chance (EPSS)
0.61%
Chance of exploitation in the next 30 days. Higher than 49.16% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-1289 Improper Validation of Unsafe Equivalence in Input
Fix
None yet
No fixed version published

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 .

Affected versions

npm

PackageVulnerableFixed in
angular
>= 1.3.0-rc.4, <= 1.8.3
No fix yet

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Attack vector
Network
Attack complexity
Low
Attack requirements
Present
Privileges required
None
User interaction
None
Confidentiality (vulnerable system)
Low
Integrity (vulnerable system)
Low
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None
Exploit maturity
Proof of concept

CVSS 3.1 4.8

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

Weakness

CWE-1289: Improper Validation of Unsafe Equivalence in Input

The product receives an input value that is used as a resource identifier or other type of reference, but it does not validate or incorrectly validates that the input is equivalent to a potentially-unsafe value.

How to prevent it
  • Implementation: Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as "red" or "blue." Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code's environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-7x27-g8rg-x87w
Angular's deprecated package has a Cross-Site Scripting issue
High Also affects angular
GHSA-j58c-ww9w-pwp5
AngularJS improperly sanitizes SVG elements
Medium Also affects angular
GHSA-mqm9-c95h-x2p6
AngularJS allows attackers to bypass common image source restrictions
Medium Also affects angular
GHSA-4w4v-5hc9-xrr2
angular vulnerable to super-linear runtime due to backtracking
High Also affects angular
GHSA-qwqh-hm9m-p5hr
angular vulnerable to regular expression denial of service via the <input type="url"> element
Medium Also affects angular
GHSA-2qqx-w9hr-q5gx
angular vulnerable to regular expression denial of service via the $resource service
Medium Also affects angular
GHSA-2vrf-hf26-jrp5
angular vulnerable to regular expression denial of service via the angular.copy() utility
Medium Also affects angular
GHSA-prc3-vjfx-vhm9
Angular (deprecated package) Cross-site Scripting
Medium Also affects angular
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor