{"answers":{"affected":"It affects 7 products.","exploited":"There is no known exploitation of CVE-2019-19397 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-19397 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-19397 is a high-severity vulnerability in S12700;S1700;S2700;S5700;S6700;S7700;S9700, published on 13 Dec 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-19397 and fix it if it is affected.\n\nWhat it is: CVE-2019-19397 is a high-severity vulnerability in S12700;S1700;S2700;S5700;S6700;S7700;S9700, published on 13 Dec 2019. 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-2019-19397 in the wild and no public exploit code.\n\nAffected product: S12700;S1700;S2700;S5700;S6700;S7700;S9700. 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-2019-19397/ (Markdown: https://insights.sbomify.com/CVE-2019-19397/index.md)","id":"CVE-2019-19397","markdown":"https://insights.sbomify.com/CVE-2019-19397/index.md","name":"CVE-2019-19397","record":{"aliases":["GHSA-c9p4-g3wp-gpxv"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Huawei network switch","requires_auth":"none","summary":"Attackers can exploit weak default algorithms in Huawei switches to cause information leaks.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"s12700_firmware","vendor":"huawei"},{"product":"s1700_firmware","vendor":"huawei"},{"product":"s2700_firmware","vendor":"huawei"},{"product":"s5700_firmware","vendor":"huawei"},{"product":"s6700_firmware","vendor":"huawei"},{"product":"s7700_firmware","vendor":"huawei"},{"product":"s9700_firmware","vendor":"huawei"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"There is a weak algorithm vulnerability in some Huawei products. The affected products use weak algorithms by default. Attackers may exploit the vulnerability to cause information leaks.","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":"Weak cryptography in S12700;S1700;S2700;S5700;S6700;S7700;S9700","id":"CVE-2019-19397","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in M5 lite 10","id":"CVE-2019-19398"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2019-19396"},"products":["S12700;S1700;S2700;S5700;S6700;S7700;S9700"],"published":"2019-12-13","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":"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can exploit weak default algorithms in Huawei switches to cause information leaks.","url":"https://insights.sbomify.com/CVE-2019-19397/"}