CWE-829: Inclusion of Functionality from Untrusted Control Sphere
The build files indicate that this project is resolving dependencies over HTTP instead of HTTPS. Any of these artifacts could have been MITM to maliciously compromise them and infect the build artifacts that were produced. Additionally, if any of these JAR files were compromised, any developers using these could continue to be infected past updating to fix this.
|
p2Repository = "http://download.eclipse.org/tools/cdt/releases/${VER_ECLIPSE_CDT}" |
|
p2Repository = "http://dist.springsource.org/release/GRECLIPSE/e${VER_ECLIPSE}" |
|
p2Repository = "http://download.eclipse.org/webtools/repository/${VER_ECLIPSE_WTP}" |
This vulnerability has a CVSS v3.0 Base Score of 8.1/10
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
This isn't just theoretical; POC code exists already to maliciously compromise jar file inflight.
See:
To fix: We need to update our build.gradle so that artifacts are resolved over HTTPS instead of HTTP.
I've been finding this vulnerability in a lot of places today and have responsibly disclosed it to some of the larger organizations involved.
CWE-829: Inclusion of Functionality from Untrusted Control Sphere
The build files indicate that this project is resolving dependencies over HTTP instead of HTTPS. Any of these artifacts could have been MITM to maliciously compromise them and infect the build artifacts that were produced. Additionally, if any of these JAR files were compromised, any developers using these could continue to be infected past updating to fix this.
spotless/_ext/eclipse-cdt/build.gradle
Line 6 in 366c1b9
spotless/_ext/eclipse-groovy/build.gradle
Line 6 in 96e74ec
spotless/_ext/eclipse-wtp/build.gradle
Line 6 in e1734c0
This vulnerability has a CVSS v3.0 Base Score of 8.1/10
https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
This isn't just theoretical; POC code exists already to maliciously compromise jar file inflight.
See:
To fix: We need to update our
build.gradleso that artifacts are resolved over HTTPS instead of HTTP.I've been finding this vulnerability in a lot of places today and have responsibly disclosed it to some of the larger organizations involved.