CVE-2024-22416 Cross-Site Request Forgery on any API call in pyLoad may lead to admin privilege escalation

Critical 9.7 Published Updated

Unauthenticated attackers can perform CSRF attacks on pyLoad API calls to escalate privileges due to missing SameSite cookie restrictions.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
A user has to click or open something
Fix
Available

What is CVE-2024-22416?

CVE-2024-22416 is a critical vulnerability in pyload, published on 17 Jan 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

Official description

pyLoad is a free and open-source Download Manager written in pure Python. The `pyload` API allows any API call to be made using GET requests. Since the session cookie is not set to `SameSite: strict`, this opens the library up to severe attack possibilities via a Cross-Site Request Forgery (CSRF) attack. As a result any API call can be made via a CSRF attack by an unauthenticated user. This issue has been addressed in release `0.5.0b3.dev78`. All users are advised to upgrade.

Weakness: CWE-352

Which versions are affected by CVE-2024-22416?

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

PackageAffectedFixed in
pyload-ng PyPIAll versions0.5.0b3.dev78
pyload-ng PyPIAll versions0.5.0b3.dev78
pyload-ng PyPIAll versions0.5.0b3.dev78

Products include Pyload-Ng Project Pyload-Ng.

How do I fix CVE-2024-22416?

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

Is CVE-2024-22416 being exploited?

There is no known exploitation of CVE-2024-22416 in the wild and no public exploit code.

Public exploit code: 1 proofs of concept on GitHub.

Sources

Also known as GHSA-pgpj-v85q-h5fm, PYSEC-2024-17.

Is CVE-2024-22416 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free