# CVE-2024-21645: pyLoad Log Injection

> Unauthenticated attackers can inject arbitrary messages into pyLoad logs, potentially covering tracks or framing others.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jan 2024
- **Updated:** 14 Nov 2024
- **Also known as:** GHSA-ghmw-rwh8-6qmr, PYSEC-2026-1818

## What is CVE-2024-21645?

CVE-2024-21645 is a medium-severity vulnerability in pyload, published on 8 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

pyLoad is the free and open-source Download Manager written in pure Python. A log injection vulnerability was identified in `pyload` allowing any unauthenticated actor to inject arbitrary messages into the logs gathered by `pyload`. Forged or otherwise, corrupted log files can be used to cover an attacker’s tracks or even to implicate another party in the commission of a malicious act. This vulnerability has been patched in version 0.5.0b3.dev77.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

3 open source packages ship an affected version, including pyload-ng. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pyload-ng` | PyPI | All versions | 0.5.0b3.dev77 |
| `pyload-ng` | PyPI | All versions | 0.5.0b3.dev77 |
| `pyload-ng` | PyPI | All versions | 0.5.0b3.dev77 |

Products: Pyload Pyload.

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

Upgrade pyload-ng to 0.5.0b3.dev77 or later.

## Is CVE-2024-21645 being exploited?

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

Public exploit code:

- pyload - Log Injection (nuclei): http/cves/2024/CVE-2024-21645.yaml

## Other vulnerabilities in pyload

- [CVE-2023-0297](https://insights.sbomify.com/CVE-2023-0297/): Code Injection in pyload/pyload (critical 9.8)
- [CVE-2026-33992](https://insights.sbomify.com/CVE-2026-33992/): pyLoad: Server-Side Request Forgery via Download Link Submission Enables Cloud Metadata Exfiltration (critical 9.3)
- [CVE-2024-47821](https://insights.sbomify.com/CVE-2024-47821/): pyLoad vulnerable to remote code execution by download to /.pyload/scripts using /flashgot API (critical 9.1)
- [CVE-2024-32880](https://insights.sbomify.com/CVE-2024-32880/): pyLoad allows upload to arbitrary folder lead to RCE (critical 9.1)
- [CVE-2026-41133](https://insights.sbomify.com/CVE-2026-41133/): pyLoad has Stale Session Privilege After Role/Permission Change (Privilege Revocation Bypass) (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-21645 is a medium-severity vulnerability in pyload, published on 8 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-21645 exists.

Affected packages and fixed versions:
- pyload-ng (PyPI): affected all versions; fixed in 0.5.0b3.dev77
- pyload-ng (PyPI): affected all versions; fixed in 0.5.0b3.dev77
- pyload-ng (PyPI): affected all versions; fixed in 0.5.0b3.dev77

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

## Sources

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

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