block repositories using http by default
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.8.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
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
Timeline
- CVE published
- Record last updated
Affected versions
- Apache Software Foundation Apache Maven
through 3.8.1
- org.apache.maven:maven-compatMaven
fixed in 3.8.1
- org.apache.maven:maven-coreMaven
fixed in 3.8.1
References 25
lists.apache.org
- thread.html/r9a027668558264c4897633e66bcb7784099fdec9f9b22c38c2442f00@<users.maven.apache.org>
- thread.html/r06db4057b74e0598a412734f693a34a8836ac6f06d16d139e5e1027c@<dev.maven.apache.org>
- thread.html/r0556ce5db7231025785477739ee416b169d8aff5ee9bac7854d64736@<announce.apache.org>
- thread.html/ra88a0eba7f84658cefcecc0143fd8bbad52c229ee5dfcbfdde7b6457@<dev.jena.apache.org>
- thread.html/r3f0450dcab7e63b5f233ccfbc6fca5f1867a75c8aa2493ea82732381@<dev.jena.apache.org>
- thread.html/rfc27e2727a20a574f39273e0432aa97486a332f9b3068f6ac1346594@<dev.myfaces.apache.org>
- thread.html/r86e1c81e03f441855f127980e9b3d41939d04a7caea2b7ab718e2288@<jira.kafka.apache.org>
- thread.html/red3bf6cbfd99e36b0c0a4fa1cea1eef1eb300c6bd8f372f497341265@<dev.kafka.apache.org>
- thread.html/r340e75c9bb6e8661b89e1cf2c52f4638a18312e57bd884722bc28f52@<jira.kafka.apache.org>
- thread.html/r78fb6d2cf0ca332cfa43abd4471e75fa6c517ed9cdfcb950bff48d40@<jira.kafka.apache.org>
- thread.html/r39fa6ec4b7e912d3e04ea68efd23e554ec9c8efa2c96f5b45104fc61@<jira.kafka.apache.org>
- thread.html/r30e9fcba679d164158cc26236704c351954909c18cb2485d11038aa6@<dev.kafka.apache.org>
- thread.html/rc7ae2530063d1cd1cf8e9fa130d10940760f927168d4063d23b8cd0a@<commits.kafka.apache.org>
- thread.html/r5ae6aaa8a2ce86145225c3516bb45d315c0454e3765d651527e5df8a@<commits.kafka.apache.org>
- thread.html/r0a5e4ff2a7ca7ad8595d7683afbaeb3b8788ba974681907f97e7dc8e@<jira.kafka.apache.org>
- thread.html/r86aebd0387ae19b740b3eb28bad83fe6aceca0d6257eaa810a6e0002@<commits.kafka.apache.org>
- thread.html/r2721aba31a8562639c4b937150897e24f78f747cdbda8641c0f659fe@<users.kafka.apache.org>
- thread.html/r71bc13669be84c2ff45b74a67929bc2da905c152e12a39b406e3c2a0@<issues.karaf.apache.org>
- thread.html/r53cd5de57aaa126038c5301d8f518f3defab3c5b1c7e17c97bad08d8@<issues.karaf.apache.org>
- thread.html/r52c6cda14dc6315dc79e72d30109f4589e9c6300ef6dc1a019da32d4@<issues.karaf.apache.org>
- thread.html/r74329c671df713f61ae4620ee2452a0443ccad7f33c60e8ed7d21ff9@<issues.karaf.apache.org>
- thread.html/r07a89b32783f73bda6903c1f9aadeb859e5bef0a4daed6d87db8e4a9@<issues.karaf.apache.org>
- thread.html/r96cc126d3ee9aa42af9d3bb4baa94828b0a5f656584a50dcc594125f@<issues.karaf.apache.org>