{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-21814 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-21814 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-21814 is a high-severity memory corruption vulnerability in AT\u0026T, published on 13 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-21814 and fix it if it is affected.\n\nWhat it is: CVE-2021-21814 is a high-severity memory corruption vulnerability in AT\u0026T, published on 13 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-21814 in the wild and no public exploit code.\n\nAffected product: AT\u0026T. 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-21814/ (Markdown: https://insights.sbomify.com/CVE-2021-21814/index.md)","id":"CVE-2021-21814","markdown":"https://insights.sbomify.com/CVE-2021-21814/index.md","name":"CVE-2021-21814","record":{"aliases":["GHSA-9m22-mqrh-x6c3"],"analysis":{"component_type":"other","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"AT\u0026T software","requires_auth":"low_privilege","summary":"An attacker can trigger memory corruption via a buffer overflow in HandleFileArg by providing a long command-line argument, potentially leading to code execution or crashes.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"talos","cpe":[{"product":"xmill","vendor":"att"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-88","name":"Improper Neutralization of Argument Delimiters in a Command"}],"description":"Within the function HandleFileArg the argument filepattern is under control of the user who passes it in from the command line. filepattern is passed directly to strlen to determine the ending location of the char* passed in by the user, no checks are done to see if the passed in char* is longer than the staticly sized buffer data is memcpy‘d into, but after the memcpy a null byte is written to what is assumed to be the end of the buffer to terminate the char*, but without length checks, this null write occurs at an arbitrary offset from the buffer. An attacker can provide malicious input to trigger this vulnerability.","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 AT\u0026T","id":"CVE-2021-21814","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 AT\u0026T","id":"CVE-2021-21815"},"packages":[],"prev":{"headline":"Memory corruption in AT\u0026T","id":"CVE-2021-21813"},"products":["AT\u0026T"],"published":"2021-08-13","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2022-26507","kev_date_added":null,"published":"2022-04-14"},{"cvss_score":8.1,"headline":"Memory corruption in AT\u0026T","id":"CVE-2021-21811","kev_date_added":null,"published":"2021-08-31"},{"cvss_score":8.1,"headline":"Memory corruption in AT\u0026T","id":"CVE-2021-21826","kev_date_added":null,"published":"2021-08-20"},{"cvss_score":8.1,"headline":"Memory corruption in AT\u0026T","id":"CVE-2021-21827","kev_date_added":null,"published":"2021-08-20"},{"cvss_score":8.1,"headline":"Memory corruption in AT\u0026T","id":"CVE-2021-21828","kev_date_added":null,"published":"2021-08-20"},{"cvss_score":8.1,"headline":"Memory corruption in AT\u0026T","id":"CVE-2021-21825","kev_date_added":null,"published":"2021-08-18"},{"cvss_score":8.1,"headline":"Memory corruption in AT\u0026T Labs","id":"CVE-2021-21810","kev_date_added":null,"published":"2021-08-17"}],"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 can trigger memory corruption via a buffer overflow in HandleFileArg by providing a long command-line argument, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2021-21814/"}