Skip to content

yt-dlp File Downloader cookie leak

Moderate severity GitHub Reviewed Published Jul 6, 2023 in yt-dlp/yt-dlp • Updated Nov 10, 2023

Package

pip yt-dlp (pip)

Affected versions

< 2023.7.06

Patched versions

2023.7.06

Description

Impact

During file downloads, yt-dlp or the external downloaders that yt-dlp employs may leak cookies on HTTP redirects to a different host, or leak them when the host for download fragments differs from their parent manifest's host.

This vulnerable behavior is present in all versions of youtube-dl, youtube-dlc and yt-dlp released since 2015.01.25. All native and external downloaders are affected, except for curl and httpie (httpie version 3.1.0 or later).

At the file download stage, all cookies are passed by yt-dlp to the file downloader as a Cookie header, thereby losing their scope. This also occurs in yt-dlp's info JSON output, which may be used by external tools. As a result, the downloader or external tool may indiscriminately send cookies with requests to domains or paths for which the cookies are not scoped.

An example of a potential attack scenario exploiting this vulnerability:

  1. an attacker has crafted a malicious website with an embedded URL designed to be detected by yt-dlp as a video download. This embedded URL has the domain of a trusted site that the user has loaded cookies for, and conducts an unvalidated redirect to a target URL.
  2. yt-dlp extracts this URL and calculates a Cookie header based on its domain for the file downloader to make its request(s) with.
  3. the download URL redirects to a server controlled by the attacker, to which yt-dlp forwards the user's sensitive cookie information.

Patches

yt-dlp version 2023.07.06 fixes this issue by doing the following:

  • Remove the Cookie header upon HTTP redirects
  • Have native downloaders calculate their own Cookie header from the cookiejar
  • Utilize external downloaders' built-in support for cookies instead of passing them as header arguments
  • If the external downloader does not have proper cookie support, then disable HTTP redirection (axel only)
  • Process cookies passed as HTTP headers to limit their scope (--add-header "Cookie:..." is scoped to input URL domain only)
  • Store cookies in a separate cookies field of the info dict instead of http_headers so as not to lose their scope

Patches for youtube-dl are expected and we will update this advisory when they are merged.

Workarounds

It is recommended to upgrade yt-dlp to version 2023.07.06 as soon as possible.

For users who are not able to upgrade:

  • Avoid using cookies and user authentication methods (--cookies, --cookies-from-browser, --username, --password, --netrc). While extractors may set custom cookies, these usually do not contain sensitive information.
  • Avoid using --load-info-json

Or, if authentication is a must:

  • Verify the integrity of download links from unknown sources in browser (including redirects) before passing them to yt-dlp
  • Use curl as external downloader, since it is not impacted (--downloader curl)
  • Avoid fragmented formats such as HLS/m3u8, DASH/mpd and ISM (use -f "(bv*+ba/b)[protocol~='^https?$']")

References

References

@coletdjnz coletdjnz published to yt-dlp/yt-dlp Jul 6, 2023
Published to the GitHub Advisory Database Jul 6, 2023
Reviewed Jul 6, 2023
Published by the National Vulnerability Database Jul 6, 2023
Last updated Nov 10, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:N/A:N

EPSS score

0.229%
(61st percentile)

CVE ID

CVE-2023-35934

GHSA ID

GHSA-v8mc-9377-rwjj

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.