Malicious dependency code via HTTP repositories
Published Apr 23, 2021 · Updated Aug 3, 2024
Origin validation in Apache Maven 3.8.1 and earlier allows remote attackers to execute malicious dependency code via HTTP repositories. Maven follows repository URLs declared in dependency POM files without enforcing HTTPS or validating that the repository origin is trustworthy, so a hijacked or impersonated repository can supply altered artifacts. The attack requires a build to resolve a dependency from such a repository; centrally managed repositories avoid this exposure.
Summary
What happened
Origin validation in Apache Maven 3.8.1 and earlier allows remote attackers to execute malicious dependency code via HTTP repositories. Maven follows repository URLs declared in dependency POM files without enforcing HTTPS or validating that the repository origin is trustworthy, so a hijacked or impersonated repository can supply altered artifacts. The attack requires a build to resolve a dependency from such a repository; centrally managed repositories avoid this exposure.
The record
- CVE
- CVE-2021-26291
- Published
- Apr 23, 2021
- Updated
- Aug 3, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Maven
- Classifications
- CWE-346, T1195.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 23, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Apache Maven <=3.8.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo