{"answers":{"affected":"It affects 15 products.","exploited":"There is no known exploitation of CVE-2021-33478 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-33478 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-33478 is a medium-severity memory corruption vulnerability in n/a, published on 22 Jul 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-33478 and fix it if it is affected.\n\nWhat it is: CVE-2021-33478 is a medium-severity memory corruption vulnerability in n/a, published on 22 Jul 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-33478 in the wild and no public exploit code.\n\nAffected product: n/a. 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-33478/ (Markdown: https://insights.sbomify.com/CVE-2021-33478/index.md)","id":"CVE-2021-33478","markdown":"https://insights.sbomify.com/CVE-2021-33478/index.md","name":"CVE-2021-33478","record":{"aliases":["GHSA-vh28-q6j2-63w7"],"analysis":{"component_type":"hardware_firmware","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Cisco IP Phone firmware","requires_auth":"none","summary":"An attacker with physical access can achieve arbitrary code execution in the TrustZone TEE of affected Cisco IP phones by manipulating chip pins.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ip_phone_8800_firmware","vendor":"cisco"},{"product":"ip_phone_8800_series_with_multiplatform_firmware","vendor":"cisco"},{"product":"ip_phone_8811_firmware","vendor":"cisco"},{"product":"ip_phone_8811_with_multiplatform_firmware","vendor":"cisco"},{"product":"ip_phone_8841_firmware","vendor":"cisco"},{"product":"ip_phone_8841_with_multiplatform_firmware","vendor":"cisco"},{"product":"ip_phone_8845_firmware","vendor":"cisco"},{"product":"ip_phone_8845_with_multiplatform_firmware","vendor":"cisco"},{"product":"ip_phone_8851_firmware","vendor":"cisco"},{"product":"ip_phone_8851_with_multiplatform_firmware","vendor":"cisco"},{"product":"ip_phone_8861_firmware","vendor":"cisco"},{"product":"ip_phone_8861_with_multiplatform_firmware","vendor":"cisco"},{"product":"ip_phone_8865_firmware","vendor":"cisco"},{"product":"ip_phone_8865_with_multiplatform_firmware","vendor":"cisco"},{"product":"wireless_ip_phone_8821_firmware","vendor":"cisco"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-119","name":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}],"description":"The TrustZone implementation in certain Broadcom MediaxChange firmware could allow an unauthenticated, physically proximate attacker to achieve arbitrary code execution in the TrustZone Trusted Execution Environment (TEE) of an affected device. This, for example, affects certain Cisco IP Phone and Wireless IP Phone products before 2021-07-07. Exploitation is possible only when the attacker can disassemble the device in order to control the voltage/current for chip pins.","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":"Memory corruption in n/a","id":"CVE-2021-33478","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in gocr","id":"CVE-2021-33479"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2021-33477"},"products":["n/a"],"published":"2021-07-22","related":[{"cvss_score":7.5,"headline":"Cisco IP Phone 8800 Series File Upload Denial of Service Vulnerability","id":"CVE-2019-1766","kev_date_added":null,"published":"2019-03-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-08-03","vendors":["n/a"]},"summary":"An attacker with physical access can achieve arbitrary code execution in the TrustZone TEE of affected Cisco IP phones by manipulating chip pins.","url":"https://insights.sbomify.com/CVE-2021-33478/"}