{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-3571 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-3571 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-3571 is a medium-severity vulnerability in Facebook WhatsApp Desktop, published on 16 Jul 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-3571 and fix it if it is affected.\n\nWhat it is: CVE-2019-3571 is a medium-severity vulnerability in Facebook WhatsApp Desktop, published on 16 Jul 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-3571 in the wild and no public exploit code.\n\nAffected product: Facebook WhatsApp Desktop. 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-3571/ (Markdown: https://insights.sbomify.com/CVE-2019-3571/index.md)","id":"CVE-2019-3571","markdown":"https://insights.sbomify.com/CVE-2019-3571/index.md","name":"CVE-2019-3571","record":{"aliases":["GHSA-78r4-4fjf-6phv"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"WhatsApp Desktop","requires_auth":"none","summary":"Malicious clients can send files displayed with incorrect extensions, potentially misleading users about file types.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"facebook","cpe":[{"product":"whatsapp","vendor":"whatsapp"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"}],"description":"An input validation issue affected WhatsApp Desktop versions prior to 0.3.3793 which allows malicious clients to send files to users that would be displayed with a wrong extension.","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 WhatsApp Desktop","id":"CVE-2019-3571","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2019-3572"},"packages":[],"prev":{"headline":"Memory corruption in HHVM","id":"CVE-2019-3570"},"products":["WhatsApp Desktop"],"published":"2019-07-16","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":"Malicious clients can send files displayed with incorrect extensions, potentially misleading users about file types.","url":"https://insights.sbomify.com/CVE-2019-3571/"}