Maven traffic interception via HTTP repository access
Published Jan 30, 2020 · Updated Aug 4, 2024
Improper certificate validation in JetBrains IntelliJ IDEA before 2019.3 allows remote attackers to intercept Maven repository traffic via HTTP. Maven repository resolution uses plain HTTP for some repositories instead of HTTPS, removing transport confidentiality and integrity protections. Man-in-the-middle attackers can read or alter repository responses delivered to the IDE.
Summary
What happened
Improper certificate validation in JetBrains IntelliJ IDEA before 2019.3 allows remote attackers to intercept Maven repository traffic via HTTP. Maven repository resolution uses plain HTTP for some repositories instead of HTTPS, removing transport confidentiality and integrity protections. Man-in-the-middle attackers can read or alter repository responses delivered to the IDE.
The record
- CVE
- CVE-2020-7904
- Published
- Jan 30, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-295, T1557
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 30, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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