{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-6827 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-6827 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-6827 is a medium-severity vulnerability in n/a, published on 26 Sep 2016. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-6827 and fix it if it is affected.\n\nWhat it is: CVE-2016-6827 is a medium-severity vulnerability in n/a, published on 26 Sep 2016. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-6827 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-6827/ (Markdown: https://insights.sbomify.com/CVE-2016-6827/index.md)","id":"CVE-2016-6827","markdown":"https://insights.sbomify.com/CVE-2016-6827/index.md","name":"CVE-2016-6827","record":{"aliases":["GHSA-5h6j-66w2-pcp6"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Huawei FusionCompute","requires_auth":"low_privilege","summary":"Remote authenticated users can obtain sensitive information because Huawei FusionCompute stores cleartext AES keys in a file.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fusioncompute","vendor":"huawei"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Huawei FusionCompute before V100R005C10CP7002 stores cleartext AES keys in a file, which allows remote authenticated users to obtain sensitive information via unspecified vectors.","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":"Information disclosure in n/a","id":"CVE-2016-6827","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2016"},"n_packages":0,"n_references":3,"next":{"headline":"Use after free in n/a","id":"CVE-2016-6828"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2016-6826"},"products":["n/a"],"published":"2016-09-26","related":[{"cvss_score":9.1,"headline":"Auth bypass in FusionCompute","id":"CVE-2020-9233","kev_date_added":null,"published":"2020-08-17"},{"cvss_score":8.8,"headline":"Other in FusionCompute","id":"CVE-2020-9236","kev_date_added":null,"published":"2024-12-27"},{"cvss_score":8.8,"headline":"Command injection in FusionCompute","id":"CVE-2021-37102","kev_date_added":null,"published":"2021-11-23"},{"cvss_score":8.8,"headline":"Command injection in FusionCompute","id":"CVE-2020-9242","kev_date_added":null,"published":"2020-08-17"},{"cvss_score":7.8,"headline":"Privilege escalation in FusionCompute","id":"CVE-2020-9114","kev_date_added":null,"published":"2020-12-01"},{"cvss_score":7.8,"headline":"Privilege escalation in FusionCompute","id":"CVE-2020-9078","kev_date_added":null,"published":"2020-08-10"},{"cvss_score":7.5,"headline":"File upload in FusionCompute","id":"CVE-2021-37105","kev_date_added":null,"published":"2021-09-28"}],"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":"Remote authenticated users can obtain sensitive information because Huawei FusionCompute stores cleartext AES keys in a file.","url":"https://insights.sbomify.com/CVE-2016-6827/"}