{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2020-9252 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-9252 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-9252 is a low-severity path traversal vulnerability in HUAWEI Mate 20, published on 17 Jul 2020. 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-2020-9252 and fix it if it is affected.\n\nWhat it is: CVE-2020-9252 is a low-severity path traversal vulnerability in HUAWEI Mate 20, published on 17 Jul 2020. 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-2020-9252 in the wild and no public exploit code.\n\nAffected product: HUAWEI Mate 20. 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-2020-9252/ (Markdown: https://insights.sbomify.com/CVE-2020-9252/index.md)","id":"CVE-2020-9252","markdown":"https://insights.sbomify.com/CVE-2020-9252/index.md","name":"CVE-2020-9252","record":{"aliases":["GHSA-9v6x-99vx-fw68"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei smartphone OS","requires_auth":"high_privilege","summary":"Attackers can write files to arbitrary paths on Huawei Mate 20 and Honor Magic2 devices due to insufficient pathname validation.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"magic2_firmware","vendor":"huawei"},{"product":"mate_20_firmware","vendor":"huawei"},{"product":"mate_20_rs_firmware","vendor":"huawei"},{"product":"mate_20_x_firmware","vendor":"huawei"}],"cvss":{"score":2.3,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"HUAWEI Mate 20 versions earlier than 10.1.0.160(C00E160R3P8), HUAWEI Mate 20 X versions earlier than 10.1.0.135(C00E135R2P8), HUAWEI Mate 20 RS versions earlier than 10.1.0.160(C786E160R3P8), and Honor Magic2 smartphones versions earlier than 10.1.0.160(C00E160R2P11) have a path traversal vulnerability. The system does not sufficiently validate certain pathname from certain process, successful exploit could allow the attacker write files to a crafted path.","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":"Path traversal in HUAWEI Mate 20","id":"CVE-2020-9252","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in Lion-AL00C","id":"CVE-2020-9253"},"packages":[],"prev":{"headline":"Missing authorization in HUAWEI Mate 20","id":"CVE-2020-9251"},"products":["HUAWEI Mate 20","HUAWEI Mate 20 RS","HUAWEI Mate 20 X","Honor Magic2"],"published":"2020-07-17","related":[],"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-04","vendors":["n/a"]},"summary":"Attackers can write files to arbitrary paths on Huawei Mate 20 and Honor Magic2 devices due to insufficient pathname validation.","url":"https://insights.sbomify.com/CVE-2020-9252/"}