{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-20096 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-20096 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-20096 is a medium-severity vulnerability in n/a, published on 23 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-20096 and fix it if it is affected.\n\nWhat it is: CVE-2020-20096 is a medium-severity vulnerability in n/a, published on 23 Mar 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-20096 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-2020-20096/ (Markdown: https://insights.sbomify.com/CVE-2020-20096/index.md)","id":"CVE-2020-20096","markdown":"https://insights.sbomify.com/CVE-2020-20096/index.md","name":"CVE-2020-20096","record":{"aliases":["GHSA-vg5v-c82v-59w5"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"WhatsApp mobile app","requires_auth":"none","summary":"Attackers can spoof URIs in WhatsApp messages due to improper UI representation, potentially misleading users about link destinations.","user_interaction":"required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"whatsapp","vendor":"whatsapp"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[],"description":"Whatsapp iOS 2.19.80 and prior and Android 2.19.222 and prior user interface does not properly represent URI messages to the user, which results in URI spoofing via specially crafted messages.","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-2020-20096","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2020-20118"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2020-20095"},"products":["n/a"],"published":"2022-03-23","related":[{"cvss_score":9.8,"headline":"WhatsApp VOIP Stack Buffer Overflow","id":"CVE-2019-3568","kev_date_added":"2022-04-19","published":"2019-05-14"},{"cvss_score":8.2,"headline":"WhatsApp Cross-Site Scripting","id":"CVE-2019-18426","kev_date_added":"2022-05-23","published":"2020-01-21"},{"cvss_score":5.4,"headline":"Meta Platforms WhatsApp Incorrect Authorization","id":"CVE-2025-55177","kev_date_added":"2025-09-02","published":"2025-08-29"},{"cvss_score":9.8,"headline":"Integer overflow in WhatsApp Business for Android","id":"CVE-2022-36934","kev_date_added":null,"published":"2022-09-22"},{"cvss_score":9.8,"headline":"Memory corruption in WhatsApp Business for Android","id":"CVE-2021-24042","kev_date_added":null,"published":"2022-01-04"},{"cvss_score":9.8,"headline":"Memory corruption in WhatsApp Business for Android","id":"CVE-2021-24041","kev_date_added":null,"published":"2021-12-07"},{"cvss_score":9.8,"headline":"Memory corruption in WhatsApp Business for Android","id":"CVE-2021-24026","kev_date_added":null,"published":"2021-04-06"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can spoof URIs in WhatsApp messages due to improper UI representation, potentially misleading users about link destinations.","url":"https://insights.sbomify.com/CVE-2020-20096/"}