ManageIQ / ManageIQ/ui-components

CVE-2024-8372 (Medium) detected in angular-1.8.3.tgz

Open
#496 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Mend: dependency security vulnerability stale
Dominant language
TypeScript
Stars
16
Forks
55
PR merge metrics
No merged PRs in 30d

Description

## CVE-2024-8372 - Medium Severity Vulnerability
Vulnerable Library - angular-1.8.3.tgz

HTML enhanced for web apps


Library home page: https://registry.npmjs.org/angular/-/angular-1.8.3.tgz


Sample Path to Dependency File: /package.json


Path to vulnerable library: /home/wss-scanner/.yarn/berry/cache/angular-npm-1.8.3-0e5e833690-10.zip


Dependency Hierarchy:
- angular-ui-sortable-0.19.0.tgz (Root Library)
- :x: **angular-1.8.3.tgz** (Vulnerable Library)

Found in HEAD commit: a5db0714038685437d759b29eb80b4b9e415b2c2


Found in base branch: master



Vulnerability Details



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 .
Mend Note: The description of this vulnerability differs from MITRE.

Publish Date: 2024-09-09

URL: CVE-2024-8372



CVSS 3 Score Details (4.8)

Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: Low
- Availability Impact: Low


For more information on CVSS3 Scores, click here.

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with package.json and the dependency hierarchy showing angular-ui-sortable-0.19.0.tgz pulling in angular-1.8.3.tgz. Read the CVE-2024-8372 details and AngularJS support-status information, then determine an appropriate supported remediation for the end-of-life dependency. Done means the vulnerable dependency path is addressed and the security scan no longer reports this CVE.

Written by the indexing model from the issue text.

Assessment

Tech stack
angularjs
Domain
frontend, security
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.