CVE-2022-0768

Server-Side Request Forgery (SSRF) in rudloff/alltube

References

• https://github.com/Rudloff/alltube/commit/3a4f09dda0a466662a4e52cde674749e0c668e8d
• https://github.com/Rudloff/alltube/commit/1b099bb9836a3ce7c427a41722a7ab5a3d1c1b2d
• https://huntr.dev/bounties/9b14cc46-ec08-4940-83cc-9f986b2a5903/
• https://nvd.nist.gov/vuln/detail/CVE-2022-0768
• https://github.com/ytdl-org/youtube-dl/issues/30691

Releases prior to 3.0.2 are vulnerable to a Server-Side Request Forgery vulnerability that allows an attacker to send a request to an internal hostname.

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2022-0768 has a CVSS score of 9.1 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.0.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

3.0.2 contains a fix for this vulnerability.
(The 1.x and 2.x releases are not maintained anymore.)

Part of the fix requires applying a patch to youtube-dl to prevent it from following HTTP redirects. If you are using the version of youtube-dl bundled with 3.0.2, it is already patched.
However, if you are using your own unpatched version of youtube-dl you might still be vulnerable.

1. What is CVE-2022-0768? CVE-2022-0768 is a critical-severity server-side request forgery (SSRF) vulnerability in rudloff/alltube (composer), affecting versions < 3.0.2. It is fixed in 3.0.2. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
2. How severe is CVE-2022-0768? CVE-2022-0768 has a CVSS score of 9.1 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of rudloff/alltube are affected by CVE-2022-0768? rudloff/alltube (composer) versions < 3.0.2 is affected.
4. Is there a fix for CVE-2022-0768? Yes. CVE-2022-0768 is fixed in 3.0.2. Upgrade to this version or later.
5. Is CVE-2022-0768 exploitable, and should I be worried? Whether CVE-2022-0768 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-0768 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-0768? Upgrade rudloff/alltube to 3.0.2 or later.

Other vulnerabilities in rudloff/alltube