# CVE-2024-42370: Litestar repository vulnerable to Environment Variable injection in `docs-preview.yml` workflow

> Attackers can inject environment variables in the docs-preview workflow to exfiltrate secrets and manipulate repository content.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Aug 2024
- **Updated:** 19 Aug 2024
- **Also known as:** GHSA-4hq2-rpgc-r8r7

## What is CVE-2024-42370?

CVE-2024-42370 is a high-severity code injection vulnerability in litestar-org litestar, published on 9 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Litestar is an Asynchronous Server Gateway Interface (ASGI) framework. In versions 2.10.0 and prior, Litestar's `docs-preview.yml` workflow is vulnerable to Environment Variable injection which may lead to secret exfiltration and repository manipulation. This issue grants a malicious actor the permission to write issues, read metadata, and write pull requests. In addition, the `DOCS_PREVIEW_DEPLOY_TOKEN` is exposed to the attacker. Commit 84d351e96aaa2a1338006d6e7221eded161f517b contains a fix for this issue.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2024-42370?

2 open source packages ship an affected version, including litestar.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `litestar` | PyPI | All versions to 2.10.0 | None |
| `litestar` | PyPI | All versions to 2.10.0 | None |

## How do I fix CVE-2024-42370?

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

## Is CVE-2024-42370 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-42370 exists.

Public exploit code:

- Authorized security-research lab: reproduction of CVE-2024-42370 / GHSA-4hq2-rpgc-r8r7 (env injection in docs-preview.yml) — snapshot of litestar-org/litestar@18d84d84 (github_poc): https://github.com/pvharmo2/gha-lab-ba8e0c4217

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-42370 and fix it if it is affected.

What it is: CVE-2024-42370 is a high-severity code injection vulnerability in litestar-org litestar, published on 9 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-42370 exists.

Affected packages and fixed versions:
- litestar (PyPI): affected all versions up to 2.10.0; no fix listed
- litestar (PyPI): affected all versions up to 2.10.0; 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-2024-42370/ (Markdown: https://insights.sbomify.com/CVE-2024-42370/index.md)
```

## Sources

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

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