{"answers":{"affected":"1 open source package ship an affected version, including embano1/wip. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-30623 in the wild and no public exploit code.","fix":"Upgrade embano1/wip to 2 or later.","what":"CVE-2023-30623 is a high-severity command injection vulnerability in embano1 wip, published on 24 Apr 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-30623 and fix it if it is affected.\n\nWhat it is: CVE-2023-30623 is a high-severity command injection vulnerability in embano1 wip, published on 24 Apr 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-30623 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- embano1/wip (GitHub Actions): affected all versions; fixed in 2\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-30623/ (Markdown: https://insights.sbomify.com/CVE-2023-30623/index.md)","id":"CVE-2023-30623","markdown":"https://insights.sbomify.com/CVE-2023-30623/index.md","name":"CVE-2023-30623","record":{"aliases":["GHSA-rg3q-prf8-qxmp"],"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 on CI runners by injecting code into pull request titles, potentially stealing secrets.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wip","vendor":"wip_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":"`embano1/wip` is a GitHub Action written in Bash. Prior to version 2, the  `embano1/wip` action uses the `github.event.pull_request.title` parameter in an insecure way. The title parameter is used in a run statement - resulting in a command injection vulnerability due to string interpolation. This vulnerability can be triggered by any user on GitHub. They just need to create a pull request with a commit message containing an exploit. (Note that first-time PR requests will not be run - but the attacker can submit a valid PR before submitting an invalid PR). The commit can be genuine, but the commit message can be malicious. This can be used to execute code on the GitHub runners and can be used to exfiltrate any secrets used in the CI pipeline, including repository tokens. Version 2 has a fix for this issue.","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":"Arbitrary command injection in embano1/wip","id":"CVE-2023-30623","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"GitHub Actions","product":null,"products":[],"type":"command_injection","year":"2023"},"n_packages":1,"n_references":3,"next":{"headline":"Wasmtime has Undefined Behavior in Rust runtime functions","id":"CVE-2023-30624"},"packages":[{"ecosystem":"GitHub Actions","fixed":["2"],"introduced":["0"],"last_affected":[],"package":"embano1/wip","purl":null,"source":"GHSA-rg3q-prf8-qxmp"}],"prev":{"headline":"Clusternet has potential risk which can be leveraged to make a cluster-level privilege escalation","id":"CVE-2023-30622"},"products":["wip"],"published":"2023-04-24","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-12","vendors":["embano1"]},"summary":"Attackers can execute arbitrary commands on CI runners by injecting code into pull request titles, potentially stealing secrets.","url":"https://insights.sbomify.com/CVE-2023-30623/"}