{"answers":{"affected":"1 open source package ship an affected version, including rlespinasse/github-slug-action. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-27581 in the wild and no public exploit code.","fix":"Upgrade rlespinasse/github-slug-action to 4.4.1 or later.","what":"CVE-2023-27581 is a high-severity command injection vulnerability in rlespinasse github-slug-action, published on 13 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-27581 and fix it if it is affected.\n\nWhat it is: CVE-2023-27581 is a high-severity command injection vulnerability in rlespinasse github-slug-action, published on 13 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-27581 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- rlespinasse/github-slug-action (GitHub Actions): affected from 4.0.0; fixed in 4.4.1\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-27581/ (Markdown: https://insights.sbomify.com/CVE-2023-27581/index.md)","id":"CVE-2023-27581","markdown":"https://insights.sbomify.com/CVE-2023-27581/index.md","name":"CVE-2023-27581","record":{"aliases":["GHSA-6q4m-7476-932w"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"GitHub Action","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code and steal secrets on GitHub runners by injecting payloads into pull request branch names.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"github-slug-action","vendor":"github-slug-action_project"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"github-slug-action is a GitHub Action to expose slug value of GitHub environment variables inside of one's GitHub workflow. Starting in version 4.0.0` and prior to version 4.4.1, this action uses the `github.head_ref` parameter in an insecure way. This vulnerability can be triggered by any user on GitHub on any workflow using the action on pull requests. They just need to create a pull request with a branch name, which can contain the attack payload. This can be used to execute code on the GitHub runners and to exfiltrate any secrets one uses in the CI pipeline. A patched action is available in version 4.4.1. No workaround is available.","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":"github-slug-action vulnerable to arbitrary code execution","id":"CVE-2023-27581","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":"Full authentication bypass if SASL authorization username is specified","id":"CVE-2023-27582"},"packages":[{"ecosystem":"GitHub Actions","fixed":["4.4.1"],"introduced":["4.0.0"],"last_affected":[],"package":"rlespinasse/github-slug-action","purl":null,"source":"GHSA-6q4m-7476-932w"}],"prev":{"headline":"CodeIgniter Shield Password Shucking Vulnerability","id":"CVE-2023-27580"},"products":["github-slug-action"],"published":"2023-03-13","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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-02-25","vendors":["rlespinasse"]},"summary":"Attackers can execute arbitrary code and steal secrets on GitHub runners by injecting payloads into pull request branch names.","url":"https://insights.sbomify.com/CVE-2023-27581/"}