CVE-2024-38519
HIGHDescription
`yt-dlp` and `youtube-dl` are command-line audio/video downloaders. Prior to the fixed versions, `yt-dlp` and `youtube-dl` do not limit the extensions of downloaded files, which could lead to arbitrary filenames being created in the download folder (and path traversal on Windows). Since `yt-dlp` and `youtube-dl` also read config from the working directory (and on Windows executables will be executed from the `yt-dlp` or `youtube-dl` directory), this could lead to arbitrary code being executed. `yt-dlp` version 2024.07.01 fixes this issue by whitelisting the allowed extensions. `youtube-dl` fixes this issue in commit `d42a222` on the `master` branch and in nightly builds tagged 2024-07-03 or later. This might mean some very uncommon extensions might not get downloaded, however it will also limit the possible exploitation surface. In addition to upgrading, have `.%(ext)s` at the end of the output template and make sure the user trusts the websites that they are downloading from. Also, make sure to never download to a directory within PATH or other sensitive locations like one's user directory, `system32`, or other binaries locations. For users who are not able to upgrade, keep the default output template (`-o "%(title)s [%(id)s].%(ext)s`); make sure the extension of the media to download is a common video/audio/sub/... one; try to avoid the generic extractor; and/or use `--ignore-config --config-location ...` to not load config from common locations.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 25% of all known CVEs.
References
Related Vulnerabilities
Other CWE-669 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2026-31431 | Medium | 5.5 | 100% | KEV | Fix |
| CVE-2002-0055 | Medium | 5.0 | 35% | - | - |
| CVE-2020-1048 | High | 7.8 | 17% | - | - |
| CVE-2021-22900 | High | 7.2 | 14% | KEV | - |
| CVE-2026-25253 | High | 8.8 | 8.0% | - | Fix |
| CVE-2020-6862 | Medium | 5.3 | 6.3% | - | - |
Common questions
How do I fix CVE-2024-38519?
No published fix for CVE-2024-38519 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2024-38519 being actively exploited?
Not that we know of. CVE-2024-38519 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.32% is the estimated probability that it will be exploited in the next 30 days. That is higher than 25% of all scored CVEs.
How severe is CVE-2024-38519?
CVE-2024-38519 has a CVSS v3 base score of 7.8, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2024-38519
Markdown
[](https://tridentstack.com/cve/CVE-2024-38519)HTML
<a href="https://tridentstack.com/cve/CVE-2024-38519"><img src="https://tridentstack.com/cve/badge/CVE-2024-38519.svg" alt="CVE-2024-38519"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2024-11-21.