{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-6604 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-6604 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-6604 is a critical vulnerability in n/a, published on 30 Jan 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-6604 and fix it if it is affected.\n\nWhat it is: CVE-2016-6604 is a critical vulnerability in n/a, published on 30 Jan 2017. 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-2016-6604 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-2016-6604/ (Markdown: https://insights.sbomify.com/CVE-2016-6604/index.md)","id":"CVE-2016-6604","markdown":"https://insights.sbomify.com/CVE-2016-6604/index.md","name":"CVE-2016-6604","record":{"aliases":["CVE-2016-11037","GHSA-9h2c-g2fg-fj6m"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Samsung Android kernel","requires_auth":"none","summary":"A null pointer dereference in the Samsung Exynos fimg2d driver allows attackers to cause a denial of service on affected Android devices.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"exynos_fimg2d","vendor":"samsung"}],"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-476","name":"NULL Pointer Dereference"}],"description":"NULL pointer dereference in Samsung Exynos fimg2d driver for Android L(5.0/5.1) and M(6.0) allows attackers to have unspecified impact via unknown vectors. The Samsung ID is SVE-2016-6382.","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":"Null dereference in n/a","id":"CVE-2016-6604","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"null_dereference","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"Auth bypass in n/a","id":"CVE-2016-6605"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2016-6603"},"products":["n/a"],"published":"2017-01-30","related":[],"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-06","vendors":["n/a"]},"summary":"A null pointer dereference in the Samsung Exynos fimg2d driver allows attackers to cause a denial of service on affected Android devices.","url":"https://insights.sbomify.com/CVE-2016-6604/"}