{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-6339 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-6339 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-6339 is a critical memory corruption vulnerability in Facebook WhatsApp Business for Android, published on 14 Jun 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-2018-6339 and fix it if it is affected.\n\nWhat it is: CVE-2018-6339 is a critical memory corruption vulnerability in Facebook WhatsApp Business for Android, published on 14 Jun 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-2018-6339 in the wild and no public exploit code.\n\nAffected product: Facebook WhatsApp Business 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-2018-6339/ (Markdown: https://insights.sbomify.com/CVE-2018-6339/index.md)","id":"CVE-2018-6339","markdown":"https://insights.sbomify.com/CVE-2018-6339/index.md","name":"CVE-2018-6339","record":{"aliases":["GHSA-wjm8-p3r4-7xgc"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WhatsApp Android app","requires_auth":"none","summary":"An off-by-one stack buffer overflow in WhatsApp for Android allows attackers to execute arbitrary code via crafted calls.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"facebook","cpe":[{"product":"whatsapp","vendor":"whatsapp"},{"product":"whatsapp_business","vendor":"whatsapp"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"},{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"When receiving calls using WhatsApp on Android, a stack allocation failed to properly account for the amount of data being passed in. An off-by-one error meant that data was written beyond the allocated space on the stack. This issue affects WhatsApp for Android starting in version 2.18.180 and was fixed in version 2.18.295. It also affects WhatsApp Business for Android starting in version v2.18.103 and was fixed in version v2.18.150.","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":"Memory corruption in WhatsApp Business for Android","id":"CVE-2018-6339","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in HHVM","id":"CVE-2018-6340"},"packages":[],"prev":{"headline":"Weak cryptography in HHVM","id":"CVE-2018-6337"},"products":["WhatsApp Business for Android","WhatsApp for Android"],"published":"2019-06-14","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":["Facebook"]},"summary":"An off-by-one stack buffer overflow in WhatsApp for Android allows attackers to execute arbitrary code via crafted calls.","url":"https://insights.sbomify.com/CVE-2018-6339/"}