{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-8129 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2017-8129 yet. Limit exposure of the affected software until one is available.","what":"CVE-2017-8129 is a critical vulnerability in Huawei Technologies Co., Ltd. UMA, published on 22 Nov 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-8129 and fix it if it is affected.\n\nWhat it is: CVE-2017-8129 is a critical vulnerability in Huawei Technologies Co., Ltd. UMA, published on 22 Nov 2017. 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-2017-8129 in the wild and no public exploit code.\n\nAffected product: Huawei Technologies Co., Ltd. UMA. 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-2017-8129/ (Markdown: https://insights.sbomify.com/CVE-2017-8129/index.md)","id":"CVE-2017-8129","markdown":"https://insights.sbomify.com/CVE-2017-8129/index.md","name":"CVE-2017-8129","record":{"aliases":["GHSA-382h-3vwf-5x2j"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Huawei UMA server","requires_auth":"none","summary":"An attacker can craft specific packets to exploit insufficient parameter validation in Huawei UMA, gaining elevated privileges.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"uma","vendor":"huawei"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"The UMA product with software V200R001 and V300R001 has a privilege elevation vulnerability due to insufficient validation or improper processing of parameters. An attacker could craft specific packets to exploit these vulnerabilities to gain elevated privileges.","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 UMA","id":"CVE-2017-8129","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in UMA","id":"CVE-2017-8130"},"packages":[],"prev":{"headline":"Privilege escalation in UMA","id":"CVE-2017-8128"},"products":["UMA"],"published":"2017-11-22","related":[{"cvss_score":9.8,"headline":"Privilege escalation in UMA","id":"CVE-2017-8117","kev_date_added":null,"published":"2017-11-22"},{"cvss_score":9.8,"headline":"Privilege escalation in UMA","id":"CVE-2017-8119","kev_date_added":null,"published":"2017-11-22"},{"cvss_score":9.8,"headline":"Privilege escalation in UMA","id":"CVE-2017-8120","kev_date_added":null,"published":"2017-11-22"},{"cvss_score":9.8,"headline":"Privilege escalation in UMA","id":"CVE-2017-8122","kev_date_added":null,"published":"2017-11-22"},{"cvss_score":9.8,"headline":"Privilege escalation in UMA","id":"CVE-2017-8123","kev_date_added":null,"published":"2017-11-22"},{"cvss_score":9.8,"headline":"Privilege escalation in UMA","id":"CVE-2017-8124","kev_date_added":null,"published":"2017-11-22"},{"cvss_score":9.8,"headline":"Privilege escalation in UMA","id":"CVE-2017-8126","kev_date_added":null,"published":"2017-11-22"}],"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-09-17","vendors":["Huawei Technologies Co., Ltd."]},"summary":"An attacker can craft specific packets to exploit insufficient parameter validation in Huawei UMA, gaining elevated privileges.","url":"https://insights.sbomify.com/CVE-2017-8129/"}