CVE-2019-16370 Use of a weak cryptographic algorithm in Gradle
Attackers can replace Gradle artifacts with malicious ones due to SHA-1 collision vulnerabilities in the PGP signing plugin.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2019-16370?
CVE-2019-16370 is a medium-severity vulnerability in n/a, published on 16 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The PGP signing plugin in Gradle before 6.0 relies on the SHA-1 algorithm, which might allow an attacker to replace an artifact with a different one that has the same SHA-1 message digest, a related issue to CVE-2005-4900.
Weakness: CWE-327
Which versions are affected by CVE-2019-16370?
2 open source packages ship an affected version, including org.gradle:gradle-core. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.gradle:gradle-core Maven | All versions | 6.0 |
org.gradle:gradle-core Maven | All versions | 6.0 |
Linux distribution packages (1)
gradle openSUSE:Tumbleweed | All versions | 4.4.1-7.2 |
Products include Gradle Gradle.
How do I fix CVE-2019-16370?
Upgrade org.gradle:gradle-core to 6.0 or later.
Is CVE-2019-16370 being exploited?
There is no known exploitation of CVE-2019-16370 in the wild and no public exploit code.
Other vulnerabilities in n/a
- CVE-2019-15052 Information disclosure in n/a
- CVE-2016-6199 Deserialization in n/a
- CVE-2021-29428 Local privilege escalation through system temporary directory
- CVE-2026-22816 Gradle fails to disable repositories which can expose builds to malicious artifacts
- CVE-2026-22865 Gradle's failure to disable repositories failing to answer can expose builds to malicious artifacts
Sources
Also known as DEBIAN-CVE-2019-16370, GHSA-hhr2-f668-ff2w, OESA-2021-1309, UBUNTU-CVE-2019-16370, openSUSE-SU-2024:10817-1.