{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-12778 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-12778 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-12778 is a high-severity authentication bypass vulnerability in n/a, published on 9 May 2019. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-12778 and fix it if it is affected.\n\nWhat it is: CVE-2017-12778 is a high-severity authentication bypass vulnerability in n/a, published on 9 May 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-12778 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-12778/ (Markdown: https://insights.sbomify.com/CVE-2017-12778/index.md)","id":"CVE-2017-12778","markdown":"https://insights.sbomify.com/CVE-2017-12778/index.md","name":"CVE-2017-12778","record":{"aliases":["GHSA-4j9x-m99x-9xm4"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"qBittorrent client","requires_auth":"low_privilege","summary":"Attackers can bypass the UI lock in qBittorrent by modifying the configuration file, gaining unauthorized access to application functions.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"qbittorrent","vendor":"qbittorrent"}],"cvss":{"score":7.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"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\\\u003cusername\u003e\\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","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Auth bypass in n/a","id":"CVE-2017-12778","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Null dereference in n/a","id":"CVE-2017-12779"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2017-12777"},"products":["n/a"],"published":"2019-05-09","related":[{"cvss_score":9.8,"headline":"qBittorrent Web UI Default Credentials Lead to RCE","id":"CVE-2023-30801","kev_date_added":null,"published":"2023-10-10"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2019-13640","kev_date_added":null,"published":"2019-07-17"},{"cvss_score":8.1,"headline":"Security feature bypass in n/a","id":"CVE-2024-51774","kev_date_added":null,"published":"2024-11-02"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2017-6503","kev_date_added":null,"published":"2017-03-06"},{"cvss_score":6.1,"headline":"Other in n/a","id":"CVE-2017-6504","kev_date_added":null,"published":"2017-03-06"},{"cvss_score":4,"headline":"Path traversal in qBittorrent","id":"CVE-2025-54310","kev_date_added":null,"published":"2025-07-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can bypass the UI lock in qBittorrent by modifying the configuration file, gaining unauthorized access to application functions.","url":"https://insights.sbomify.com/CVE-2017-12778/"}