{"answers":{"affected":"It affects 8 products.","exploited":"There is no known exploitation of CVE-2016-6518 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2016-6518 yet. Limit exposure of the affected software until one is available.","what":"CVE-2016-6518 is a high-severity denial of service vulnerability in n/a, published on 26 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-6518 and fix it if it is affected.\n\nWhat it is: CVE-2016-6518 is a high-severity denial of service vulnerability in n/a, published on 26 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2016-6518 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-6518/ (Markdown: https://insights.sbomify.com/CVE-2016-6518/index.md)","id":"CVE-2016-6518","markdown":"https://insights.sbomify.com/CVE-2016-6518/index.md","name":"CVE-2016-6518","record":{"aliases":["GHSA-fv5m-699v-qxvc"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Huawei network switch","requires_auth":"none","summary":"Remote attackers can cause denial of service on Huawei switches by sending malformed packets, leading to memory exhaustion and device restarts.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"s12700_firmware","vendor":"huawei"},{"product":"s5300_firmware","vendor":"huawei"},{"product":"s5700_firmware","vendor":"huawei"},{"product":"s6300_firmware","vendor":"huawei"},{"product":"s6700_firmware","vendor":"huawei"},{"product":"s7700_firmware","vendor":"huawei"},{"product":"s9300_firmware","vendor":"huawei"},{"product":"s9700_firmware","vendor":"huawei"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-399","name":null}],"description":"Memory leak in Huawei S9300, S5300, S5700, S6700, S7700, S9700, and S12700 devices allows remote attackers to cause a denial of service (memory consumption and restart) via a large number of malformed packets.","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-2016-6518","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2016"},"n_packages":0,"n_references":2,"next":{"headline":"Openstack Manila Persistent XSS in Metadata field","id":"CVE-2016-6519"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2016-6517"},"products":["n/a"],"published":"2016-09-26","related":[{"cvss_score":8.1,"headline":"Command injection in n/a","id":"CVE-2016-4087","kev_date_added":null,"published":"2016-05-23"},{"cvss_score":7.5,"headline":"Denial of service in S12700;S5700;S6700;S7700","id":"CVE-2021-22357","kev_date_added":null,"published":"2021-08-23"},{"cvss_score":7.5,"headline":"Weak cryptography in S12700;S1700;S2700;S5700;S6700;S7700;S9700","id":"CVE-2019-19397","kev_date_added":null,"published":"2019-12-13"},{"cvss_score":7.5,"headline":"Denial of service in S12700, S12700, S12700, S12700, S12700, S12700, S12700, S12700, S1700, S1700, S1700, S1700, S1700, S1700, S2300, S2300, S2300, S2300, S2300, S2300, S2300, S2700, S2700, S2700, S2700, S2700, S2700, S2700, S2700, S5300, S5300, S5300, S5300, S5300, S5300, S5300, S5700, S5700, S5700, S5700, S5700, S5700, S5700, S5700, S5700, S600-E, S600-E, S600-E, S600-E, S600-E, S6300, S6300, S6300, S6300, S6300, S6300, S6300, S6300, S6700, S6700, S6700, S6700, S6700, S6700, S6700, S6700, S7700, S7700, S7700, S7700, S7700, S7700, S7700, S7700, S7700, S7900, S7900, S7900, S9300, S9300, S9300, S9300, S9300, S9300, S9300, S9300X, S9300X, S9300X, S9300X, S9700, S9700, S9700, S9700, S9700, S9700, S9700, S9700, S9700","id":"CVE-2019-5285","kev_date_added":null,"published":"2019-06-04"},{"cvss_score":7.5,"headline":"Denial of service in S12700, S5700, S6700, S7700, S9700","id":"CVE-2016-8786","kev_date_added":null,"published":"2018-03-09"},{"cvss_score":7.5,"headline":"Integer overflow in S12700,S5700,S6700,S7700,S9700","id":"CVE-2017-17300","kev_date_added":null,"published":"2018-02-15"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2015-3913","kev_date_added":null,"published":"2017-06-08"}],"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 attackers can cause denial of service on Huawei switches by sending malformed packets, leading to memory exhaustion and device restarts.","url":"https://insights.sbomify.com/CVE-2016-6518/"}