[SECURITY] Releases are built/executed/released in the context of insecure/untrusted code
See original GitHub issueCWE-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.
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:
- https://max.computer/blog/how-to-take-over-the-computer-of-any-java-or-clojure-or-scala-developer/
- https://github.com/mveytsman/dilettante
To fix: Update your build.gradle
so that artifacts are resolved over HTTPS instead of HTTP.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (3 by maintainers)
The forge one should be https, I think it wasn’t available as https back then, thanks for the hint. The others are private repositories, not all of which support https, or built on the same buildserver, using the local repo.
@Claytonol99 as said in the email, you are subscribed to this thread, all the emails are automated, we don’t trigger it.