{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-22303 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-22303 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-22303 is a low-severity use after free vulnerability in Taurus-AL00A, published on 6 Feb 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2021-22303 and fix it if it is affected.\n\nWhat it is: CVE-2021-22303 is a low-severity use after free vulnerability in Taurus-AL00A, published on 6 Feb 2021. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2021-22303 in the wild and no public exploit code.\n\nAffected product: Taurus-AL00A. 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-22303/ (Markdown: https://insights.sbomify.com/CVE-2021-22303/index.md)","id":"CVE-2021-22303","markdown":"https://insights.sbomify.com/CVE-2021-22303/index.md","name":"CVE-2021-22303","record":{"aliases":["GHSA-p269-cjrj-rq9c"],"analysis":{"component_type":"mobile_application","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Huawei mobile device","requires_auth":"none","summary":"Attackers can cause a module crash and service disruption via a pointer double free vulnerability in Huawei Taurus devices.","user_interaction":"required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"huawei","cpe":[{"product":"taurus-al00a_firmware","vendor":"huawei"}],"cvss":{"score":3.3,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-415","name":"Double Free"}],"description":"There is a pointer double free vulnerability in Taurus-AL00A 10.0.0.1(C00E1R1P1). There is a lack of muti-thread protection when a function is called. Attackers can exploit this vulnerability by performing malicious operation to cause pointer double free. This may lead to module crash, compromising 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":"Use after free in Taurus-AL00A","id":"CVE-2021-22303","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Use after free in Taurus-AL00A","id":"CVE-2021-22304"},"packages":[],"prev":{"headline":"Memory corruption in Taurus-AL00A","id":"CVE-2021-22302"},"products":["Taurus-AL00A"],"published":"2021-02-06","related":[{"cvss_score":7.1,"headline":"Memory corruption in Taurus-AL00A","id":"CVE-2021-22302","kev_date_added":null,"published":"2021-02-06"},{"cvss_score":5.5,"headline":"Use after free in Taurus-AL00A","id":"CVE-2020-9093","kev_date_added":null,"published":"2020-12-29"},{"cvss_score":5.5,"headline":"Information disclosure in Taurus-AL00A","id":"CVE-2020-9087","kev_date_added":null,"published":"2020-10-12"},{"cvss_score":3.3,"headline":"Use after free in Taurus-AL00A","id":"CVE-2021-22304","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 cause a module crash and service disruption via a pointer double free vulnerability in Huawei Taurus devices.","url":"https://insights.sbomify.com/CVE-2021-22303/"}