{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-8769 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8769 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8769 is a medium-severity vulnerability in n/a, published on 18 May 2017. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-8769 and fix it if it is affected.\n\nWhat it is: CVE-2017-8769 is a medium-severity vulnerability in n/a, published on 18 May 2017. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-8769 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-2017-8769/ (Markdown: https://insights.sbomify.com/CVE-2017-8769/index.md)","id":"CVE-2017-8769","markdown":"https://insights.sbomify.com/CVE-2017-8769/index.md","name":"CVE-2017-8769","record":{"aliases":["GHSA-hfjp-gqm3-83qg"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WhatsApp Messenger","requires_auth":"none","summary":"Deleted chat files remain accessible in cleartext on the SD card, allowing attackers with device access to recover sensitive media.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"whatsapp","vendor":"whatsapp"}],"cvss":{"score":4.6,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"description":"Facebook WhatsApp Messenger before 2.16.323 for Android uses the SD card for cleartext storage of files (Audio, Documents, Images, Video, and Voice Notes) associated with a chat, even after that chat is deleted. There may be users who expect file deletion to occur upon chat deletion, or who expect encryption (consistent with the application's use of an encrypted database to store chat text). NOTE: the vendor reportedly indicates that they do not \"consider these to be security issues\" because a user may legitimately want to preserve any file for use \"in other apps like the Google Photos gallery\" regardless of whether its associated chat is deleted","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 n/a","id":"CVE-2017-8769","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2017-8770"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2017-8768"},"products":["n/a"],"published":"2017-05-18","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-05","vendors":["n/a"]},"summary":"Deleted chat files remain accessible in cleartext on the SD card, allowing attackers with device access to recover sensitive media.","url":"https://insights.sbomify.com/CVE-2017-8769/"}