Summary
It was discovered that Gradle used an insecure HTTP URL to download
dependencies when the built-in JavaScript or CoffeeScript Gradle plugins
were used. A remote unauthenticated attacker could possibly use this issue
to perform a machine-in-the-middle attack. (CVE-2019-11065)
It was discovered that the PGP signing plugin in Gradle relied on the
insecure SHA-1 algorithm. An attacker could possibly use this issue to
conduct spoofing attacks. (CVE-2019-16370)
Fixed packages 1
| Release | Package | Fixed in |
|---|---|---|
| Ubuntu · Pro 18.04 LTS Pro:18.04:LTS | gradle | 4.4.1-5ubuntu2~18.04+esm1 |
Vulnerabilities 2
-
Medium 5.9
Insecure transport protocol in Gradle
Gradle versions from 1.4 to 5.3.1 use an insecure HTTP URL to download dependencies when the built-in JavaScript or CoffeeScript Gradle plugins are used. Dependency artifacts could have been maliciously compromised by a MITM attack against the ajax.googleapis…
-
Low —
Use of a weak cryptographic algorithm in Gradle
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.