{"answers":{"affected":"1 open source package ship an affected version, including tj-actions/changed-files. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-51664 exists.","fix":"Upgrade tj-actions/changed-files to 41 or later.","what":"CVE-2023-51664 is a high-severity command injection vulnerability in tj-actions changed-files, published on 27 Dec 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-51664 and fix it if it is affected.\n\nWhat it is: CVE-2023-51664 is a high-severity command injection vulnerability in tj-actions changed-files, published on 27 Dec 2023. Any signed-in user can exploit it over the network, 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-2023-51664 exists.\n\nAffected packages and fixed versions:\n- tj-actions/changed-files (GitHub Actions): affected all versions; fixed in 41\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-2023-51664/ (Markdown: https://insights.sbomify.com/CVE-2023-51664/index.md)","id":"CVE-2023-51664","markdown":"https://insights.sbomify.com/CVE-2023-51664/index.md","name":"CVE-2023-51664","record":{"aliases":["GHSA-mcph-m25j-8j63"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub Actions","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary commands and leak secrets via malicious filenames in the tj-actions/changed-files GitHub Action.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"changed-files","vendor":"tj-actions"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"},{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"tj-actions/changed-files is a Github action to retrieve all files and directories. Prior to 41.0.0, the `tj-actions/changed-files` workflow allows for command injection in changed filenames, allowing an attacker to execute arbitrary code and potentially leak secrets. This issue may lead to arbitrary command execution in the GitHub Runner. This vulnerability has been addressed in version 41.0.0. Users are advised to upgrade.","ecosystems":["GitHub Actions"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"tj-actions/changed-files command injection in output filenames","id":"CVE-2023-51664","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"GitHub Actions","product":null,"products":[],"type":"command_injection","year":"2023"},"n_packages":1,"n_references":4,"next":{"headline":"Audiobookshelf vulnerable to Blind SSRF in `Auth.js`","id":"CVE-2023-51665"},"packages":[{"ecosystem":"GitHub Actions","fixed":["41"],"introduced":["0"],"last_affected":[],"package":"tj-actions/changed-files","purl":null,"source":"GHSA-mcph-m25j-8j63"}],"prev":{"headline":"Hail authentication can be bypassed by changing email address","id":"CVE-2023-51663"},"products":["changed-files"],"published":"2023-12-27","related":[{"cvss_score":8.6,"headline":"tj-actions/changed-files GitHub Action Embedded Malicious Code","id":"CVE-2025-30066","kev_date_added":"2025-03-18","published":"2025-03-15"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-25","vendors":["tj-actions"]},"summary":"Attackers can execute arbitrary commands and leak secrets via malicious filenames in the tj-actions/changed-files GitHub Action.","url":"https://insights.sbomify.com/CVE-2023-51664/"}