{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-9578 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2019-9578 is a high-severity vulnerability in n/a, published on 5 Mar 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-9578 and fix it if it is affected.\n\nWhat it is: CVE-2019-9578 is a high-severity vulnerability in n/a, published on 5 Mar 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-9578 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-9578/ (Markdown: https://insights.sbomify.com/CVE-2019-9578/index.md)","id":"CVE-2019-9578","markdown":"https://insights.sbomify.com/CVE-2019-9578/index.md","name":"CVE-2019-9578","record":{"aliases":["DEBIAN-CVE-2019-9578","GHSA-6c8w-rwwq-6qqh","UBUNTU-CVE-2019-9578"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"U2F host library","requires_auth":"none","summary":"A parsing error in the U2F host library leaks uninitialized stack memory to the device, potentially exposing sensitive data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"libu2f-host","vendor":"yubico"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-908","name":"Use of Uninitialized Resource"}],"description":"In devs.c in Yubico libu2f-host before 1.1.8, the response to init is misparsed, leaking uninitialized stack memory back to the device.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2019-9578","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":8,"next":{"headline":"Missing authorization in n/a","id":"CVE-2019-9579"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-9576"},"products":["n/a"],"published":"2019-03-05","related":[],"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-04","vendors":["n/a"]},"summary":"A parsing error in the U2F host library leaks uninitialized stack memory to the device, potentially exposing sensitive data.","url":"https://insights.sbomify.com/CVE-2019-9578/"}