In Eclipse Buildship versions prior to 3.1.1, 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 JARs or other dependencies were compromised, any developers using these could continue to be infected past updating to fix this.
The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.
The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere, in a manner that provides unintended control over that resource.
| Link | Tags |
|---|---|
| https://bugs.eclipse.org/bugs/show_bug.cgi?id=547734 | vendor advisory |
| https://github.com/eclipse/buildship/issues/855 | issue tracking exploit third party advisory |