# CVE-2020-10800: Machine-In-The-Middle in lix

> Man-in-the-middle attackers can execute arbitrary code by manipulating HTTP responses in the lix npm package.

- **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:** 21 Mar 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-q8xg-8xwf-m598

## What is CVE-2020-10800?

CVE-2020-10800 is a high-severity code injection vulnerability in n/a, published on 21 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

lix through 15.8.7 allows man-in-the-middle attackers to execute arbitrary code by modifying the HTTP client-server data stream so that the Location header is associated with attacker-controlled executable content in the postDownload field.

## Which versions are affected by CVE-2020-10800?

2 open source packages ship an affected version, including lix. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lix` | npm | All versions to 15.11.4 | None |
| `lix` | npm | All versions to 15.11.4 | None |

Products: Lix Project Lix.

## How do I fix CVE-2020-10800?

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

## Is CVE-2020-10800 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10800 and fix it if it is affected.

What it is: CVE-2020-10800 is a high-severity code injection vulnerability in n/a, published on 21 Mar 2020. 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-2020-10800 in the wild and no public exploit code.

Affected packages and fixed versions:
- lix (npm): affected all versions up to 15.11.4; no fix listed
- lix (npm): affected all versions up to 15.11.4; no fix listed

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-2020-10800/ (Markdown: https://insights.sbomify.com/CVE-2020-10800/index.md)
```

## Sources

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

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