{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-32471 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-32471 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-32471 is a high-severity code injection vulnerability in n/a, published on 10 May 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-32471 and fix it if it is affected.\n\nWhat it is: CVE-2021-32471 is a high-severity code injection vulnerability in n/a, published on 10 May 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-32471 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-32471/ (Markdown: https://insights.sbomify.com/CVE-2021-32471/index.md)","id":"CVE-2021-32471","markdown":"https://insights.sbomify.com/CVE-2021-32471/index.md","name":"CVE-2021-32471","record":{"aliases":["GHSA-wqw3-6p9p-84x8"],"analysis":{"component_type":"other","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Turing Machine implementation","requires_auth":"low_privilege","summary":"Insufficient input validation in a theoretical Turing Machine implementation allows arbitrary code execution via crafted data, though it has no real-world implications.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"universal_turing_machine","vendor":"mit"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Insufficient input validation in the Marvin Minsky 1967 implementation of the Universal Turing Machine allows program users to execute arbitrary code via crafted data. For example, a tape head may have an unexpected location after the processing of input composed of As and Bs (instead of 0s and 1s). NOTE: the discoverer states \"this vulnerability has no real-world implications.\"","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2021-01-21","github_poc":1,"max_poc_stars":79,"metasploit":0,"nuclei":0,"refs":[{"date":"2021-01-21T10:39:42Z","kind":"github_poc","ref":"https://github.com/intrinsic-propensity/turing-machine","stars":79,"title":"A Python program implementing and exploiting the Minsky Turing machine considered in the paper \"Intrinsic Propensity for Vulnerability in Computers? Arbitrary Code Execution in the Universal Turing Machine\" as per CVE-2021-32471 (https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-32471)"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2021-32471","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Moodle Exposure of Sensitive Information to an Unauthorized Actor","id":"CVE-2021-32472"},"packages":[],"prev":{"headline":"Craft CMS Cross-site Scripting Vulnerability","id":"CVE-2021-32470"},"products":["n/a"],"published":"2021-05-10","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"Insufficient input validation in a theoretical Turing Machine implementation allows arbitrary code execution via crafted data, though it has no real-world implications.","url":"https://insights.sbomify.com/CVE-2021-32471/"}