Skip to content

Origin Validation Error in Apache Maven

Critical severity GitHub Reviewed Published Jun 16, 2021 to the GitHub Advisory Database • Updated Aug 15, 2023

Package

maven org.apache.maven:maven-compat (Maven)

Affected versions

< 3.8.1

Patched versions

3.8.1
maven org.apache.maven:maven-core (Maven)
< 3.8.1
3.8.1

Description

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

References

Published by the National Vulnerability Database Apr 23, 2021
Reviewed Apr 26, 2021
Published to the GitHub Advisory Database Jun 16, 2021
Last updated Aug 15, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

EPSS score

0.305%
(69th percentile)

Weaknesses

CVE ID

CVE-2021-26291

GHSA ID

GHSA-2f88-5hg8-9x2x

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.