{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-6179 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-6179 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-6179 is a high-severity vulnerability in n/a, published on 7 Sep 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-2016-6179 and fix it if it is affected.\n\nWhat it is: CVE-2016-6179 is a high-severity vulnerability in n/a, published on 7 Sep 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-2016-6179 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-6179/ (Markdown: https://insights.sbomify.com/CVE-2016-6179/index.md)","id":"CVE-2016-6179","markdown":"https://insights.sbomify.com/CVE-2016-6179/index.md","name":"CVE-2016-6179","record":{"aliases":["GHSA-q49g-q9qj-46qw"],"analysis":{"component_type":"mobile_application","fix_type":"upgrade","impacts":["privilege_escalation","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei Honor 6","requires_auth":"none","summary":"Attackers can cause system crashes or gain privileges on Huawei Honor 6 devices via a crafted application exploiting the WiFi driver.","user_interaction":"required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"honor_6_firmware","vendor":"huawei"}],"cvss":{"score":7,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"The WiFi driver in Huawei Honor 6 smartphones with software H60-L01 before H60-L01C00B850, H60-L11 before H60-L11C00B850, H60-L21 before H60-L21C00B850, H60-L02 before H60-L02C00B850, H60-L12 before H60-L12C00B850, and H60-L03 before H60-L03C01B850 allows attackers to cause a denial of service (system crash) or gain privileges via a crafted application.","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":"Privilege escalation in n/a","id":"CVE-2016-6179","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2016-6180"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2016-6178"},"products":["n/a"],"published":"2016-09-07","related":[{"cvss_score":7.8,"headline":"Memory corruption in H60 (Honor 6), P9 Plus","id":"CVE-2016-8783","kev_date_added":null,"published":"2018-03-09"},{"cvss_score":7.8,"headline":"Memory corruption in P9,Honor 6 Versions before EVA-AL10C00B192,Versions before H60-L02 6.10.1","id":"CVE-2016-8759","kev_date_added":null,"published":"2017-04-02"},{"cvss_score":7.8,"headline":"Memory corruption in P9,Honor 6 Versions before EVA-AL10C00B192,Versions before H60-L02 6.10.1","id":"CVE-2016-8760","kev_date_added":null,"published":"2017-04-02"},{"cvss_score":7.8,"headline":"Memory corruption in P9,Honor 6 Versions before EVA-AL10C00B192,Versions before H60-L02 6.10.1","id":"CVE-2016-8761","kev_date_added":null,"published":"2017-04-02"},{"cvss_score":7.8,"headline":"Privilege escalation in Honor 6,Honor 6 Plus,Honor 7 Versions earlier than 6.9.16","id":"CVE-2016-8768","kev_date_added":null,"published":"2017-04-02"}],"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 cause system crashes or gain privileges on Huawei Honor 6 devices via a crafted application exploiting the WiFi driver.","url":"https://insights.sbomify.com/CVE-2016-6179/"}