{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-22397 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-22397 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-22397 is a medium-severity vulnerability in ManageOne, published on 2 Aug 2021. 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-2021-22397 and fix it if it is affected.\n\nWhat it is: CVE-2021-22397 is a medium-severity vulnerability in ManageOne, published on 2 Aug 2021. 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-2021-22397 in the wild and no public exploit code.\n\nAffected product: ManageOne. 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-2021-22397/ (Markdown: https://insights.sbomify.com/CVE-2021-22397/index.md)","id":"CVE-2021-22397","markdown":"https://insights.sbomify.com/CVE-2021-22397/index.md","name":"CVE-2021-22397","record":{"aliases":["GHSA-4g2x-v66g-vw9g"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei ManageOne","requires_auth":"high_privilege","summary":"Attackers can escalate privileges in Huawei ManageOne by exploiting insufficient verification of external parameters in certain files.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"manageone","vendor":"huawei"}],"cvss":{"score":6.7,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"There is a privilege escalation vulnerability in Huawei ManageOne 8.0.0. External parameters of some files are lack of verification when they are be called. Attackers can exploit this vulnerability by performing these files to cause privilege escalation attack. This can compromise normal service.","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 ManageOne","id":"CVE-2021-22397","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"privilege_escalation","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Security feature bypass in Hulk-AL00C;Jennifer-AN00C;Jenny-AL10B;OxfordPL-AN10B","id":"CVE-2021-22398"},"packages":[],"prev":{"headline":"Privilege escalation in eCNS280 TD;eSE620X vESS","id":"CVE-2021-22396"},"products":["ManageOne"],"published":"2021-08-02","related":[{"cvss_score":7.8,"headline":"Privilege escalation in ManageOne","id":"CVE-2021-22314","kev_date_added":null,"published":"2021-03-22"},{"cvss_score":7.5,"headline":"Denial of service in ManageOne","id":"CVE-2019-5289","kev_date_added":null,"published":"2019-11-13"},{"cvss_score":7.2,"headline":"Privilege escalation in ManageOne","id":"CVE-2021-22311","kev_date_added":null,"published":"2021-03-22"},{"cvss_score":7.2,"headline":"Command injection in ManageOne","id":"CVE-2020-9115","kev_date_added":null,"published":"2020-11-30"},{"cvss_score":6.5,"headline":"Denial of service in ManageOne","id":"CVE-2021-22339","kev_date_added":null,"published":"2021-05-20"},{"cvss_score":6.5,"headline":"Business logic in ManageOne","id":"CVE-2021-22298","kev_date_added":null,"published":"2021-02-06"}],"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-03","vendors":["n/a"]},"summary":"Attackers can escalate privileges in Huawei ManageOne by exploiting insufficient verification of external parameters in certain files.","url":"https://insights.sbomify.com/CVE-2021-22397/"}