{"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-2020-13295 in the wild and no public exploit code.","fix":"Upgrade gitlab-runner to a fixed version for your release line: 13.0.12, 13.1.6 or 13.2.3.","what":"CVE-2020-13295 is a medium-severity server-side request forgery vulnerability in GitLab Runner, published on 10 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-13295 and fix it if it is affected.\n\nWhat it is: CVE-2020-13295 is a medium-severity server-side request forgery vulnerability in GitLab Runner, published on 10 Aug 2020. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-13295 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- gitlab-runner (Bitnami): affected from 1.0.0; fixed in 13.0.12, 13.1.6, 13.2.3\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-2020-13295/ (Markdown: https://insights.sbomify.com/CVE-2020-13295/index.md)","id":"CVE-2020-13295","markdown":"https://insights.sbomify.com/CVE-2020-13295/index.md","name":"CVE-2020-13295","record":{"aliases":["BIT-gitlab-runner-2020-13295","GHSA-83vw-qmcc-rxwg","UBUNTU-CVE-2020-13295"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"GitLab Runner","requires_auth":"low_privilege","summary":"Attackers can exploit SSRF in GitLab Runner by replacing dockerd with a malicious server, potentially accessing internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitLab","cpe":[{"product":"runner","vendor":"gitlab"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"For GitLab Runner before 13.0.12, 13.1.6, 13.2.3, by replacing dockerd with a malicious server, the Shared Runner is susceptible to SSRF.","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":"Server-side request forgery in GitLab Runner","id":"CVE-2020-13295","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"ssrf","year":"2020"},"n_packages":1,"n_references":3,"next":{"headline":"Missing authorization in GitLab","id":"CVE-2020-13296"},"packages":[{"ecosystem":"Bitnami","fixed":["13.0.12","13.1.6","13.2.3"],"introduced":["1.0.0","13.1.0","13.2.0"],"last_affected":[],"package":"gitlab-runner","purl":"pkg:bitnami/gitlab-runner","source":"BIT-gitlab-runner-2020-13295"}],"prev":{"headline":"Missing authorization in GitLab","id":"CVE-2020-13294"},"products":["GitLab Runner"],"published":"2020-08-10","related":[{"cvss_score":6,"headline":"Misconfiguration in GitLab Runner","id":"CVE-2020-13327","kev_date_added":null,"published":"2020-10-22"},{"cvss_score":4.8,"headline":"Command injection in GitLab Runner","id":"CVE-2022-2251","kev_date_added":null,"published":"2023-01-17"}],"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["GitLab"]},"summary":"Attackers can exploit SSRF in GitLab Runner by replacing dockerd with a malicious server, potentially accessing internal resources.","url":"https://insights.sbomify.com/CVE-2020-13295/"}