{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-1905 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-1905 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-1905 is a low-severity vulnerability in Facebook WhatsApp for Android, published on 6 Oct 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-1905 and fix it if it is affected.\n\nWhat it is: CVE-2020-1905 is a low-severity vulnerability in Facebook WhatsApp for Android, published on 6 Oct 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-1905 in the wild and no public exploit code.\n\nAffected product: Facebook WhatsApp for Android. 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-1905/ (Markdown: https://insights.sbomify.com/CVE-2020-1905/index.md)","id":"CVE-2020-1905","markdown":"https://insights.sbomify.com/CVE-2020-1905/index.md","name":"CVE-2020-1905","record":{"aliases":["GHSA-wprc-r97f-h356"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WhatsApp for Android","requires_auth":"none","summary":"Sequentially generated URIs allowed malicious apps to guess and access previously opened attachments in WhatsApp for Android.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"facebook","cpe":[{"product":"whatsapp","vendor":"whatsapp"}],"cvss":{"score":3.3,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"},{"id":"CWE-340","name":"Generation of Predictable Numbers or Identifiers"}],"description":"Media ContentProvider URIs used for opening attachments in other apps were generated sequentially prior to WhatsApp for Android v2.20.185, which could have allowed a malicious third party app chosen to open the file to guess the URIs for previously opened attachments until the opener app is terminated.","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":"Information disclosure in WhatsApp for Android","id":"CVE-2020-1905","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in WhatsApp Business for Android","id":"CVE-2020-1906"},"packages":[],"prev":{"headline":"Path traversal in WhatsApp Business for iOS","id":"CVE-2020-1904"},"products":["WhatsApp for Android"],"published":"2020-10-06","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":"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":["Facebook"]},"summary":"Sequentially generated URIs allowed malicious apps to guess and access previously opened attachments in WhatsApp for Android.","url":"https://insights.sbomify.com/CVE-2020-1905/"}