block repositories using http by default
Apache Software Foundation Apache Maven
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.maven:maven-compat Maven |
|
|
| org.apache.maven:maven-core Maven |
|
|
Apache Software Foundation Apache Maven
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.maven:maven-compat Maven |
|
|
| org.apache.maven:maven-core Maven |
|
|
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
From the CVE record · apache
Apache Maven may follow repository references defined in a dependency’s POM, including non-SSL HTTP references. If an attacker takes over or impersonates such a repository, builds that follow it face a potential security risk. Builds governed by a repository manager are unaffected by this legacy behavior.
Engineers using Apache Maven maven-compat or maven-core versions earlier than 3.8.1 without a repository manager should check their builds.