{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-11419 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-11419 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-11419 is a medium-severity vulnerability in n/a, published on 14 May 2019. 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-2019-11419 and fix it if it is affected.\n\nWhat it is: CVE-2019-11419 is a medium-severity vulnerability in n/a, published on 14 May 2019. 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-2019-11419 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-2019-11419/ (Markdown: https://insights.sbomify.com/CVE-2019-11419/index.md)","id":"CVE-2019-11419","markdown":"https://insights.sbomify.com/CVE-2019-11419/index.md","name":"CVE-2019-11419","record":{"aliases":["GHSA-phxr-r4xw-v9q5"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"WeChat Android app","requires_auth":"none","summary":"Attackers can crash the WeChat Android application by replacing an emoji file with a crafted file derived from the device IMEI.","user_interaction":"required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wechat","vendor":"tencent"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"vcodec2_hls_filter in libvoipCodec_v7a.so in the WeChat application through 7.0.3 for Android allows attackers to cause a denial of service (application crash) by replacing an emoji file (under the /sdcard/tencent/MicroMsg directory) with a crafted .wxgf file. The content of the replacement must be derived from the phone's IMEI. The crash occurs upon receiving a message that contains the replaced emoji.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2019-05-16","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-05-16","kind":"exploitdb","ref":"46853","stars":null,"title":"WeChat for Android 7.0.4 - 'vcodec2_hls_filter' Denial of Service"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Null dereference in n/a","id":"CVE-2019-11419","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-11426"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-11418"},"products":["n/a"],"published":"2019-05-14","related":[{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2024-40433","kev_date_added":null,"published":"2024-07-26"},{"cvss_score":8.8,"headline":"Memory corruption in WeChat","id":"CVE-2020-27874","kev_date_added":null,"published":"2021-02-10"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2021-40180","kev_date_added":null,"published":"2022-07-26"},{"cvss_score":6.5,"headline":"Information disclosure in WeChat","id":"CVE-2021-27247","kev_date_added":null,"published":"2021-04-14"},{"cvss_score":4.3,"headline":"Open redirect in WeChat","id":"CVE-2019-17151","kev_date_added":null,"published":"2020-01-07"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can crash the WeChat Android application by replacing an emoji file with a crafted file derived from the device IMEI.","url":"https://insights.sbomify.com/CVE-2019-11419/"}