{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-5231 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-5231 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-5231 is a high-severity missing authorization vulnerability in n/a, published on 30 Jun 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-5231 and fix it if it is affected.\n\nWhat it is: CVE-2016-5231 is a high-severity missing authorization vulnerability in n/a, published on 30 Jun 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-5231 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-5231/ (Markdown: https://insights.sbomify.com/CVE-2016-5231/index.md)","id":"CVE-2016-5231","markdown":"https://insights.sbomify.com/CVE-2016-5231/index.md","name":"CVE-2016-5231","record":{"aliases":["GHSA-52xj-6c8j-4pv2"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei Mate8 OS","requires_auth":"none","summary":"Attackers can bypass permission checks to delete user data on Huawei Mate8 devices using a crafted application.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mate_8_firmware","vendor":"huawei"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"Huawei Mate8 NXT-AL before NXT-AL10C00B182, NXT-CL before NXT-CL00C92B182, NXT-DL before NXT-DL00C17B182, and NXT-TL before NXT-TL00C01B182 allows attackers to bypass permission checks and delete user data via a crafted app.","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":"Missing authorization in n/a","id":"CVE-2016-5231","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2016-5232"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2016-5230"},"products":["n/a"],"published":"2016-06-30","related":[{"cvss_score":8.8,"headline":"Auth bypass in n/a","id":"CVE-2016-5230","kev_date_added":null,"published":"2016-06-30"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2016-3680","kev_date_added":null,"published":"2016-05-26"},{"cvss_score":7.8,"headline":"Memory corruption in n/a","id":"CVE-2016-3681","kev_date_added":null,"published":"2016-05-26"},{"cvss_score":7.1,"headline":"Privilege escalation in Mate 8,Mate S,P8 Versions before NXT-AL10C00B386,Versions before NXT-CL00C92B386,Versions before NXT-DL00C17B386,Versions before NXT-TL00C01B386,Versions before CRR-CL00C92B368,Versions before CRR-CL20C92B368,Versions before CRR-TL00C01B368,Versions before CRR-UL00C00B368,Versions before CRR-UL20C00B368,Versions before GRA-TL00C01B366,Versions before GRA-CL00C92B366,Versions before GRA-CL10C92B366,Versions before GRA-UL00C00B366,Versions before GRA-UL10C00B366","id":"CVE-2016-8791","kev_date_added":null,"published":"2017-04-02"},{"cvss_score":7.1,"headline":"Privilege escalation in Mate 8,Mate S,P8 Versions before NXT-AL10C00B386,Versions before NXT-CL00C92B386,Versions before NXT-DL00C17B386,Versions before NXT-TL00C01B386,Versions before CRR-CL00C92B368,Versions before CRR-CL20C92B368,Versions before CRR-TL00C01B368,Versions before CRR-UL00C00B368,Versions before CRR-UL20C00B368,Versions before GRA-TL00C01B366,Versions before GRA-CL00C92B366,Versions before GRA-CL10C92B366,Versions before GRA-UL00C00B366,Versions before GRA-UL10C00B366","id":"CVE-2016-8792","kev_date_added":null,"published":"2017-04-02"},{"cvss_score":7.1,"headline":"Privilege escalation in Mate 8,Mate S,P8 Versions before NXT-AL10C00B386,Versions before NXT-CL00C92B386,Versions before NXT-DL00C17B386,Versions before NXT-TL00C01B386,Versions before CRR-CL00C92B368,Versions before CRR-CL20C92B368,Versions before CRR-TL00C01B368,Versions before CRR-UL00C00B368,Versions before CRR-UL20C00B368,Versions before GRA-TL00C01B366,Versions before GRA-CL00C92B366,Versions before GRA-CL10C92B366,Versions before GRA-UL00C00B366,Versions before GRA-UL10C00B366","id":"CVE-2016-8794","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 bypass permission checks to delete user data on Huawei Mate8 devices using a crafted application.","url":"https://insights.sbomify.com/CVE-2016-5231/"}