{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19766 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-19766 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-19766 is a high-severity vulnerability in n/a, published on 12 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-19766 and fix it if it is affected.\n\nWhat it is: CVE-2019-19766 is a high-severity vulnerability in n/a, published on 12 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-19766 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-2019-19766/ (Markdown: https://insights.sbomify.com/CVE-2019-19766/index.md)","id":"CVE-2019-19766","markdown":"https://insights.sbomify.com/CVE-2019-19766/index.md","name":"CVE-2019-19766","record":{"aliases":["GHSA-fpv9-cq8g-9x23"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Bitwarden server","requires_auth":"none","summary":"The Bitwarden server uses a potentially weak Key Derivation Function, potentially exposing user credentials to offline brute-force attacks.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"server","vendor":"bitwarden"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-916","name":"Use of Password Hash With Insufficient Computational Effort"}],"description":"The Bitwarden server through 1.32.0 has a potentially unwanted KDF.","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":"Weak cryptography in n/a","id":"CVE-2019-19766","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Use after free in n/a","id":"CVE-2019-19767"},"packages":[],"prev":{"headline":"Unused CVE for 2019","id":"CVE-2019-19765"},"products":["n/a"],"published":"2019-12-12","related":[{"cvss_score":9.3,"headline":"Bitwarden Server \u003c 2026.6.0 Authorization Bypass via Admin Auth Request","id":"CVE-2026-60104","kev_date_added":null,"published":"2026-07-08"},{"cvss_score":8.9,"headline":"Bitwarden Server \u003c 2026.4.0 Missing Authorization via Provider Clients","id":"CVE-2026-43639","kev_date_added":null,"published":"2026-05-11"},{"cvss_score":8.6,"headline":"Bitwarden Server \u003c 2026.4.1 Authentication Bypass via SCIM API Key","id":"CVE-2026-43640","kev_date_added":null,"published":"2026-05-11"},{"cvss_score":7.5,"headline":"Server-side request forgery in n/a","id":"CVE-2020-15879","kev_date_added":null,"published":"2020-07-21"},{"cvss_score":7.1,"headline":"Bitwarden Server \u003c 2026.5.0 Privilege Escalation via Bulk User Remove Endpoint","id":"CVE-2026-57520","kev_date_added":null,"published":"2026-06-25"},{"cvss_score":5.3,"headline":"Bitwarden Server \u003c 2026.5.0 Broken Access Control via PreviewInvoiceController","id":"CVE-2026-57521","kev_date_added":null,"published":"2026-06-25"}],"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":"The Bitwarden server uses a potentially weak Key Derivation Function, potentially exposing user credentials to offline brute-force attacks.","url":"https://insights.sbomify.com/CVE-2019-19766/"}