# CVE-2024-51774: Security feature bypass in n/a

> qBittorrent fails to enforce HTTPS certificate validation, allowing attackers to bypass security checks and potentially intercept traffic.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Nov 2024
- **Updated:** 6 Nov 2024
- **Also known as:** DEBIAN-CVE-2024-51774, GHSA-hfxc-7rp9-xw9w, UBUNTU-CVE-2024-51774, openSUSE-SU-2024:0358-1, openSUSE-SU-2024:14459-1

## What is CVE-2024-51774?

CVE-2024-51774 is a high-severity vulnerability in n/a, published on 2 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

qBittorrent before 5.0.1 proceeds with use of https URLs even after certificate validation errors.

Weakness: CWE-295 (Improper Certificate Validation)

## Which versions are affected by CVE-2024-51774?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `qbittorrent` | SUSE:Package Hub 15 SP6 | All versions | 5.0.1-bp156.3.6.1 |
| `qbittorrent` | openSUSE:Leap 15.6 | All versions | 5.0.1-bp156.3.6.1 |
| `qbittorrent` | openSUSE:Tumbleweed | All versions | 5.0.1-2.1 |

Products: Qbittorrent Qbittorrent.

## How do I fix CVE-2024-51774?

Upgrade to a fixed version.

## Is CVE-2024-51774 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-51774 exists.

Public exploit code:

- qBittorrent 5.0.1 - MITM RCE (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2023-30801](https://insights.sbomify.com/CVE-2023-30801/): qBittorrent Web UI Default Credentials Lead to RCE (critical 9.8)
- [CVE-2019-13640](https://insights.sbomify.com/CVE-2019-13640/): Command injection in n/a (critical 9.8)
- [CVE-2017-12778](https://insights.sbomify.com/CVE-2017-12778/): Auth bypass in n/a (high 7.1)
- [CVE-2017-6503](https://insights.sbomify.com/CVE-2017-6503/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2017-6504](https://insights.sbomify.com/CVE-2017-6504/): Other in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-51774 and fix it if it is affected.

What it is: CVE-2024-51774 is a high-severity vulnerability in n/a, published on 2 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-51774 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-51774/ (Markdown: https://insights.sbomify.com/CVE-2024-51774/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-51774
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-51774
- OSV: https://osv.dev/vulnerability/CVE-2024-51774

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-51774/
Summaries are generated and may contain mistakes; the official description above is the record.