{"answers":{"affected":"1 open source package ship an affected version, including gitlab-runner. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-2251 in the wild and no public exploit code.","fix":"Upgrade gitlab-runner to a fixed version for your release line: 15.3.5, 15.4.4 or 15.5.2.","what":"CVE-2022-2251 is a medium-severity command injection vulnerability in GitLab Runner, published on 17 Jan 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-2022-2251 and fix it if it is affected.\n\nWhat it is: CVE-2022-2251 is a medium-severity command injection vulnerability in GitLab Runner, published on 17 Jan 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-2251 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- gitlab-runner (Bitnami): affected all versions; fixed in 15.3.5, 15.4.4, 15.5.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-2022-2251/ (Markdown: https://insights.sbomify.com/CVE-2022-2251/index.md)","id":"CVE-2022-2251","markdown":"https://insights.sbomify.com/CVE-2022-2251/index.md","name":"CVE-2022-2251","record":{"aliases":["BIT-gitlab-runner-2022-2251","GHSA-cxfq-cc8j-j2pp","UBUNTU-CVE-2022-2251"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"GitLab Runner","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary commands in GitLab Runner by crafting malicious branch names, requiring another user to trigger the pipeline.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitLab","cpe":[{"product":"runner","vendor":"gitlab"}],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"Improper sanitization of branch names in GitLab Runner affecting all versions prior to 15.3.5, 15.4 prior to 15.4.4, and 15.5 prior to 15.5.2 allows a user who creates a branch with a specially crafted name and gets another user to trigger a pipeline to execute commands in the runner as that other user.","ecosystems":["Bitnami"],"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":"Command injection in GitLab Runner","id":"CVE-2022-2251","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"command_injection","year":"2022"},"n_packages":1,"n_references":3,"next":{"headline":"Open Redirect in microweber/microweber","id":"CVE-2022-2252"},"packages":[{"ecosystem":"Bitnami","fixed":["15.3.5","15.4.4","15.5.2"],"introduced":["0","15.4.0","15.5.0"],"last_affected":[],"package":"gitlab-runner","purl":"pkg:bitnami/gitlab-runner","source":"BIT-gitlab-runner-2022-2251"}],"prev":{"headline":"Open redirect in GitLab","id":"CVE-2022-2250"},"products":["GitLab Runner"],"published":"2023-01-17","related":[{"cvss_score":6,"headline":"Misconfiguration in GitLab Runner","id":"CVE-2020-13327","kev_date_added":null,"published":"2020-10-22"},{"cvss_score":5.4,"headline":"Server-side request forgery in GitLab Runner","id":"CVE-2020-13295","kev_date_added":null,"published":"2020-08-10"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-08","vendors":["GitLab"]},"summary":"Attackers can execute arbitrary commands in GitLab Runner by crafting malicious branch names, requiring another user to trigger the pipeline.","url":"https://insights.sbomify.com/CVE-2022-2251/"}