jgeraigery / hadoop-555665675

Apache Hadoop
https://hadoop.apache.org/
Apache License 2.0
0 stars 0 forks source link

maven-core-3.0.5.jar: 1 vulnerabilities (highest severity is: 9.1) - autoclosed #128

Closed mend-for-github-com[bot] closed 3 months ago

mend-for-github-com[bot] commented 3 months ago
Vulnerable Library - maven-core-3.0.5.jar

Maven Core classes.

Library home page: http://maven.apache.org/ref/3.0.5/

Path to dependency file: /hadoop-maven-plugins/pom.xml

Path to vulnerable library: /hadoop-maven-plugins/pom.xml,/home/wss-scanner/.m2/repository/org/apache/maven/maven-core/3.0.5/maven-core-3.0.5.jar

Vulnerabilities

CVE Severity CVSS Exploit Maturity EPSS Dependency Type Fixed in (maven-core version) Remediation Possible** Reachability
CVE-2021-26291 Critical 9.1 Not Defined 0.2% maven-core-3.0.5.jar Direct org.apache.maven:maven-core:3.8.1, org.apache.maven:maven-compat:3.8.1

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2021-26291 ### Vulnerable Library - maven-core-3.0.5.jar

Maven Core classes.

Library home page: http://maven.apache.org/ref/3.0.5/

Path to dependency file: /hadoop-maven-plugins/pom.xml

Path to vulnerable library: /hadoop-maven-plugins/pom.xml,/home/wss-scanner/.m2/repository/org/apache/maven/maven-core/3.0.5/maven-core-3.0.5.jar

Dependency Hierarchy: - :x: **maven-core-3.0.5.jar** (Vulnerable Library)

Found in base branch: hubspot-3.3

### Vulnerability Details

Apache Maven will follow repositories that are defined in a dependency’s Project Object Model (pom) which may be surprising to some users, resulting in potential risk if a malicious actor takes over that repository or is able to insert themselves into a position to pretend to be that repository. Maven is changing the default behavior in 3.8.1+ to no longer follow http (non-SSL) repository references by default. More details available in the referenced urls. If you are currently using a repository manager to govern the repositories used by your builds, you are unaffected by the risks present in the legacy behavior, and are unaffected by this vulnerability and change to default behavior. See this link for more information about repository management: https://maven.apache.org/repository-management.html

Publish Date: 2021-04-23

URL: CVE-2021-26291

### Threat Assessment

Exploit Maturity: Not Defined

EPSS: 0.2%

### CVSS 3 Score Details (9.1)

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

For more information on CVSS3 Scores, click here.

### Suggested Fix

Type: Upgrade version

Origin: https://github.com/advisories/GHSA-2f88-5hg8-9x2x

Release Date: 2021-04-23

Fix Resolution: org.apache.maven:maven-core:3.8.1, org.apache.maven:maven-compat:3.8.1

:rescue_worker_helmet: Automatic Remediation will be attempted for this issue.

:rescue_worker_helmet:Automatic Remediation will be attempted for this issue.

mend-for-github-com[bot] commented 3 months ago

:heavy_check_mark: This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.