{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41226 exists.","fix":"No fix has been published for CVE-2024-41226 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-41226 is a high-severity code injection vulnerability in n/a, published on 6 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-41226 and fix it if it is affected.\n\nWhat it is: CVE-2024-41226 is a high-severity code injection vulnerability in n/a, published on 6 Aug 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-41226 exists.\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-2024-41226/ (Markdown: https://insights.sbomify.com/CVE-2024-41226/index.md)","id":"CVE-2024-41226","markdown":"https://insights.sbomify.com/CVE-2024-41226/index.md","name":"CVE-2024-41226","record":{"aliases":["GHSA-cg4j-f388-m354"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Automation Anywhere RPA","requires_auth":"none","summary":"Attackers can execute arbitrary code via CSV injection in Automation Anywhere, though the vendor disputes validity as client-side.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"automation_360","vendor":"automationanywhere"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-1236","name":"Improper Neutralization of Formula Elements in a CSV File"}],"description":"A CSV injection vulnerability in Automation Anywhere Automation 360 version 21094 allows attackers to execute arbitrary code via a crafted payload. NOTE: Automation Anywhere disputes this report, arguing the attacker executes everything from the client side and does not attack the Control Room. The payload is being injected in the http Response from the client-side, so the owner of the Response and payload is the end user in this case. They contend that the server's security controls have no impact or role to play in this situation and therefore this is not a valid vulnerability.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Code injection in n/a","id":"CVE-2024-41226","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2024-41228"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2024-41217"},"products":["n/a"],"published":"2024-08-06","related":[{"cvss_score":7.5,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-29856","kev_date_added":null,"published":"2022-04-29"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-09-03","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code via CSV injection in Automation Anywhere, though the vendor disputes validity as client-side.","url":"https://insights.sbomify.com/CVE-2024-41226/"}