# CVE-2019-11770: Supply chain in Eclipse Buildship

> Attackers can perform MITM attacks to inject malicious code into dependencies resolved over HTTP, compromising build artifacts and infecting developers.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2qmx-rjgf-q7p7

## What is CVE-2019-11770?

CVE-2019-11770 is a high-severity vulnerability in The Eclipse Foundation Eclipse Buildship, published on 14 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-669 (Incorrect Resource Transfer Between Spheres), CWE-829 (Inclusion of Functionality from Untrusted Control Sphere)

## Which versions are affected by CVE-2019-11770?

It affects 1 product.


Products: Eclipse Buildship.

## How do I fix CVE-2019-11770?

No fix has been published for CVE-2019-11770 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-11770 being exploited?

There is no known exploitation of CVE-2019-11770 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11770 and fix it if it is affected.

What it is: CVE-2019-11770 is a high-severity vulnerability in The Eclipse Foundation Eclipse Buildship, published on 14 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-11770 in the wild and no public exploit code.

Affected product: The Eclipse Foundation Eclipse Buildship. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-11770/ (Markdown: https://insights.sbomify.com/CVE-2019-11770/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-11770
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-11770
- OSV: https://osv.dev/vulnerability/CVE-2019-11770

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-11770/
Summaries are generated and may contain mistakes; the official description above is the record.