{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16992 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16992 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16992 is a high-severity vulnerability in n/a, published on 29 Sep 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-16992 and fix it if it is affected.\n\nWhat it is: CVE-2019-16992 is a high-severity vulnerability in n/a, published on 29 Sep 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-16992 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-16992/ (Markdown: https://insights.sbomify.com/CVE-2019-16992/index.md)","id":"CVE-2019-16992","markdown":"https://insights.sbomify.com/CVE-2019-16992/index.md","name":"CVE-2019-16992","record":{"aliases":["GHSA-23cv-hj48-7c4g"],"analysis":{"component_type":"mobile_application","fix_type":"no_fix_stated","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Keybase iOS app","requires_auth":"none","summary":"The Keybase iOS app may insufficiently notify users when signing cryptocurrency attestations, potentially violating user expectations regarding key usage semantics.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"keybase","vendor":"keybase"}],"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-347","name":"Improper Verification of Cryptographic Signature"}],"description":"The Keybase app 2.13.2 for iOS provides potentially insufficient notice that it is employing a user's private key to sign a certain cryptocurrency attestation (that an address at keybase.io can be used for Stellar payments to the user), which might be incompatible with a user's personal position on the semantics of an attestation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Other in n/a","id":"CVE-2019-16992","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"phpBB Cross-Site Request Forgery (CSRF)","id":"CVE-2019-16993"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-16991"},"products":["n/a"],"published":"2019-09-29","related":[{"cvss_score":9.8,"headline":"Race condition in n/a","id":"CVE-2019-7249","kev_date_added":null,"published":"2019-01-31"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-18629","kev_date_added":null,"published":"2018-12-20"},{"cvss_score":7.2,"headline":"Path traversal of file names in Keybase Client for Windows","id":"CVE-2021-34422","kev_date_added":null,"published":"2021-11-11"},{"cvss_score":5.5,"headline":"Information disclosure in n/a","id":"CVE-2021-23827","kev_date_added":null,"published":"2021-02-22"},{"cvss_score":5.3,"headline":"Arbitrary command execution in Keybase Client for Windows","id":"CVE-2021-34426","kev_date_added":null,"published":"2021-12-14"},{"cvss_score":3.7,"headline":"Retained exploded messages in Keybase clients for macOS and Windows","id":"CVE-2022-22779","kev_date_added":null,"published":"2022-02-09"}],"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 Keybase iOS app may insufficiently notify users when signing cryptocurrency attestations, potentially violating user expectations regarding key usage semantics.","url":"https://insights.sbomify.com/CVE-2019-16992/"}