{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-5821 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-5821 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-5821 is a high-severity vulnerability in n/a, published on 13 Jul 2016. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-5821 and fix it if it is affected.\n\nWhat it is: CVE-2016-5821 is a high-severity vulnerability in n/a, published on 13 Jul 2016. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-5821 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-5821/ (Markdown: https://insights.sbomify.com/CVE-2016-5821/index.md)","id":"CVE-2016-5821","markdown":"https://insights.sbomify.com/CVE-2016-5821/index.md","name":"CVE-2016-5821","record":{"aliases":["GHSA-6jrh-cqm6-j7wr"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei HiSuite","requires_auth":"low_privilege","summary":"Local attackers can gain SYSTEM privileges by replacing DLLs in the HiSuite service directory due to weak file permissions.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"hisuite","vendor":"huawei"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-264","name":null}],"description":"Huawei HiSuite before 4.0.4.204_ove (Out of China) and before 4.0.4.301 (China) use a weak ACL (FILE_WRITE_DATA for BUILTIN\\Users) for the HiSuite service directory, which allows local users to gain SYSTEM privileges via a Trojan horse (1) SspiCli.dll or (2) USERENV.dll file or possibly other unspecified DLL files.","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-5821","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2016"},"n_packages":0,"n_references":5,"next":{"headline":"Denial of service in n/a","id":"CVE-2016-5822"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2016-5820"},"products":["n/a"],"published":"2016-07-13","related":[{"cvss_score":7.8,"headline":"Other in HiSuite","id":"CVE-2020-9100","kev_date_added":null,"published":"2020-07-06"},{"cvss_score":7.8,"headline":"Supply chain in HiSuite 4.0.5.300 OVE","id":"CVE-2016-8273","kev_date_added":null,"published":"2017-04-02"},{"cvss_score":7.8,"headline":"Other in HiSuite 4.0.5.300 OVE","id":"CVE-2016-8274","kev_date_added":null,"published":"2017-04-02"},{"cvss_score":5.5,"headline":"Weak cryptography in HiSuite, HwBackup","id":"CVE-2019-5263","kev_date_added":null,"published":"2019-11-29"},{"cvss_score":5.3,"headline":"Other in HiSuite","id":"CVE-2019-5245","kev_date_added":null,"published":"2019-06-13"},{"cvss_score":5.3,"headline":"Information disclosure in HiSuite 4.0.5.300 OVE","id":"CVE-2016-8272","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":"Local attackers can gain SYSTEM privileges by replacing DLLs in the HiSuite service directory due to weak file permissions.","url":"https://insights.sbomify.com/CVE-2016-5821/"}