{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2015-8679 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-8679 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-8679 is a medium-severity denial of service vulnerability in n/a, published on 7 Apr 2016. 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-2015-8679 and fix it if it is affected.\n\nWhat it is: CVE-2015-8679 is a medium-severity denial of service vulnerability in n/a, published on 7 Apr 2016. 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-2015-8679 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-2015-8679/ (Markdown: https://insights.sbomify.com/CVE-2015-8679/index.md)","id":"CVE-2015-8679","markdown":"https://insights.sbomify.com/CVE-2015-8679/index.md","name":"CVE-2015-8679","record":{"aliases":["GHSA-2g2j-q43h-638m"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei smartphone driver","requires_auth":"none","summary":"Attackers can crash Huawei P8 and Mate S smartphones by triggering an invalid memory access in the Maxim smartpa driver via a crafted application.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mate_s_firmware","vendor":"huawei"},{"product":"p8_firmware","vendor":"huawei"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"The Maxim_smartpa_dev driver in Huawei P8 smartphones with software GRA-TL00 before GRA-TL00C01B230, GRA-CL00 before GRA-CL00C92B230, GRA-CL10 before GRA-CL10C92B230, GRA-UL00 before GRA-UL00C00B230, and GRA-UL10 before GRA-UL10C00B230 and Mate S smartphones with software CRR-TL00 before CRR-TL00C01B160SP01, CRR-UL00 before CRR-UL00C00B160, and CRR-CL00 before CRR-CL00C92B161 allow attackers to cause a denial of service (system crash) via a crafted application, which triggers an invalid memory access.","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":"Denial of service in n/a","id":"CVE-2015-8679","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2015"},"n_packages":0,"n_references":1,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2015-8680"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2015-8678"},"products":["n/a"],"published":"2016-04-07","related":[{"cvss_score":7.8,"headline":"Integer overflow in n/a","id":"CVE-2016-1495","kev_date_added":null,"published":"2016-04-13"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2015-8307","kev_date_added":null,"published":"2016-04-07"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2015-8318","kev_date_added":null,"published":"2016-04-07"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2015-8319","kev_date_added":null,"published":"2016-04-07"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2015-8680","kev_date_added":null,"published":"2016-04-07"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2015-8681","kev_date_added":null,"published":"2016-04-07"},{"cvss_score":6.1,"headline":"Information disclosure in n/a","id":"CVE-2015-8682","kev_date_added":null,"published":"2016-04-13"}],"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":"Attackers can crash Huawei P8 and Mate S smartphones by triggering an invalid memory access in the Maxim smartpa driver via a crafted application.","url":"https://insights.sbomify.com/CVE-2015-8679/"}