{"answers":{"affected":"1 open source package ship an affected version, including tj-actions/branch-names. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-49291 in the wild and no public exploit code.","fix":"Upgrade tj-actions/branch-names to 7.0.7 or later.","what":"CVE-2023-49291 is a critical code injection vulnerability in tj-actions branch-names, published on 4 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-49291 and fix it if it is affected.\n\nWhat it is: CVE-2023-49291 is a critical code injection vulnerability in tj-actions branch-names, published on 4 Dec 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-49291 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- tj-actions/branch-names (GitHub Actions): affected all versions; fixed in 7.0.7\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-49291/ (Markdown: https://insights.sbomify.com/CVE-2023-49291/index.md)","id":"CVE-2023-49291","markdown":"https://insights.sbomify.com/CVE-2023-49291/index.md","name":"CVE-2023-49291","record":{"aliases":["GHSA-8v8w-v8xg-79rf"],"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":"none","summary":"Attackers can execute arbitrary code and steal secrets by crafting malicious branch names in GitHub Actions workflows using the tj-actions/branch-names action.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"branch-names","vendor":"tj-actions"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"tj-actions/branch-names is a Github action to retrieve branch or tag names with support for all events. The `tj-actions/branch-names` GitHub Actions improperly references the `github.event.pull_request.head.ref` and `github.head_ref` context variables within a GitHub Actions `run` step. The head ref variable is the branch name and can be used to execute arbitrary code using a specially crafted branch name. As a result an attacker can use this vulnerability to steal secrets from or abuse `GITHUB_TOKEN` permissions. This vulnerability has been addressed in version 7.0.7. Users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":["GitHub Actions"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Improper Sanitization of Branch Name Leads to Arbitrary Code Injection","id":"CVE-2023-49291","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"GitHub Actions","product":null,"products":[],"type":"code_injection","year":"2023"},"n_packages":1,"n_references":5,"next":{"headline":"Possible private key restoration in go package github.com/ecies/go","id":"CVE-2023-49292"},"packages":[{"ecosystem":"GitHub Actions","fixed":["7.0.7"],"introduced":["0"],"last_affected":[],"package":"tj-actions/branch-names","purl":null,"source":"GHSA-8v8w-v8xg-79rf"}],"prev":{"headline":"Malicious parameters can cause a denial of service in lestrrat-go/jwx","id":"CVE-2023-49290"},"products":["branch-names"],"published":"2023-12-04","related":[],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-02","vendors":["tj-actions"]},"summary":"Attackers can execute arbitrary code and steal secrets by crafting malicious branch names in GitHub Actions workflows using the tj-actions/branch-names action.","url":"https://insights.sbomify.com/CVE-2023-49291/"}