Security Resilience

CVE-2024-21645

Pyload ≤ 0.4.9

Public PoC
Published
08 January 2024
Modified
17 June 2026
Patch / advisory
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
EPSS Score 0.25 98th percentile
Risk Priority 70 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2024-21645 is a medium-severity Injection (CWE-74) vulnerability in Pyload Pyload. Its CVSS base score is 5.3 (Medium).

Operationally, ranked in the top 2% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

pyLoad, the open-source Python download manager, contains a log injection vulnerability tracked as CVE-2024-21645. The flaw permits arbitrary messages to be written into the application's logs without authentication, enabling forged or corrupted log entries that could mask attacker activity or falsely implicate another party. It is rated CVSS 5.3 and is assigned CWE-74.

Any unauthenticated remote attacker can exploit the issue over the network to inject chosen content into pyLoad logs, achieving limited integrity impact without affecting confidentiality or availability.

The vulnerability was addressed in version 0.5.0b3.dev77, as detailed in the GitHub security advisory GHSA-ghmw-rwh8-6qmr and the associated commit 4159a1191ec4fe6d927e57a9c4bb8f54e16c381d.

EPSS scores reached a peak of 0.7349 with a current value of 0.6910.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

CVEs Like This One

CVE-2020-17496Shared CWE-74
CVE-2025-20281Shared CWE-74
CVE-2023-43835Shared CWE-74
CVE-2025-25477Shared CWE-74
CVE-2024-6469Shared CWE-74
CVE-2023-49964Shared CWE-74
CVE-2023-44270Shared CWE-74
CVE-2023-4818Shared CWE-74
CVE-2025-62697Shared CWE-74
CVE-2016-4010Shared CWE-74

Affected Assets

pyload
pyload
0.5.0 · ≤ 0.4.9

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SI-10 directly requires validation of information inputs to reject malformed or special-element content before it reaches downstream parsers.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.15 Logging partial match
finds

Logging supports detection of injection attempts but does not prevent the weakness.

finds

Monitoring activities can identify active injection attacks after they occur.

blocks

A.8.25 mandates a secure SDLC process that includes secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training to reduce injection flaws, but does not itself enforce or guarantee neutralization of special elements at runtime.

blocks

Application security requirements explicitly call for controls against injection attacks in software design.

blocks

A.8.27 mandates security-by-design principles (including distrust external input, data validation/sanitization, secure architecture layers, and design reviews against attack patterns) that reach injection when applied to output construction; this stops exploitation for a minority slice (e.g. where principles drive sanitization) but leaves most code-level injection defects untouched without further implementation rigor.

prevents

Secure coding standards require proper neutralization of special elements, directly addressing CWE-74.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-74, a class-level weakness, and none of its children carries one either.

References