{"answers":{"affected":"2 open source packages ship an affected version, including golang and toolchain. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-45285 in the wild and no public exploit code.","fix":"Upgrade golang to a fixed version for your release line: 1.20.12 or 1.21.5.","what":"CVE-2023-45285 is a high-severity vulnerability in Golang Go, published on 6 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-45285 and fix it if it is affected.\n\nWhat it is: CVE-2023-45285 is a high-severity vulnerability in Golang Go, published on 6 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-45285 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- golang (Bitnami): affected all versions; fixed in 1.20.12, 1.21.5\n- toolchain (Go): affected all versions; fixed in 1.20.12, 1.21.5\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-45285/ (Markdown: https://insights.sbomify.com/CVE-2023-45285/index.md)","id":"CVE-2023-45285","markdown":"https://insights.sbomify.com/CVE-2023-45285/index.md","name":"CVE-2023-45285","record":{"aliases":["AZL-32101","AZL-32103","AZL-37323","AZL-37438","AZL-79014","AZL-98985","BELL-CVE-2023-45285","BIT-golang-2023-45285","DEBIAN-CVE-2023-45285","GHSA-5f94-vhjq-rpg8","GO-2023-2383","MINI-926h-53rc-247q","UBUNTU-CVE-2023-45285"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Go toolchain","requires_auth":"none","summary":"The Go toolchain may use insecure git protocols when fetching modules directly, bypassing security checks if the module proxy is disabled.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Go","cpe":[{"product":"go","vendor":"golang"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[],"description":"Using go get to fetch a module with the \".git\" suffix may unexpectedly fallback to the insecure \"git://\" protocol if the module is unavailable via the secure \"https://\" and \"git+ssh://\" protocols, even if GOINSECURE is not set for said module. This only affects users who are not using the module proxy and are fetching modules directly (i.e. GOPROXY=off).","ecosystems":["Bitnami","Go"],"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 'go get' may unexpectedly fallback to insecure git in cmd/go","id":"CVE-2023-45285","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"golang:go","products":["golang:go"],"type":"security_feature_bypass","year":"2023"},"n_packages":2,"n_references":5,"next":{"headline":"HTTP request body disclosure in github.com/go-resty/resty/v2","id":"CVE-2023-45286"},"packages":[{"ecosystem":"Bitnami","fixed":["1.20.12","1.21.5"],"introduced":["0","1.21.0-0"],"last_affected":[],"package":"golang","purl":"pkg:bitnami/golang","source":"BIT-golang-2023-45285"},{"ecosystem":"Go","fixed":["1.20.12","1.21.5"],"introduced":["0","1.21.0-0"],"last_affected":[],"package":"toolchain","purl":"pkg:golang/toolchain","source":"GO-2023-2383"}],"prev":{"headline":"Incorrect detection of reserved device names on Windows in path/filepath","id":"CVE-2023-45284"},"products":["cmd/go"],"published":"2023-12-06","related":[{"cvss_score":8.1,"headline":"Microsoft Windows CryptoAPI Spoofing","id":"CVE-2020-0601","kev_date_added":"2021-11-03","published":"2020-01-14"},{"cvss_score":9.8,"headline":"Missing bound checks can lead to memory corruption in safe Go in cmd/compile","id":"CVE-2026-27143","kev_date_added":null,"published":"2026-04-08"},{"cvss_score":9.8,"headline":"Unexpected behavior from Is methods for IPv4-mapped IPv6 addresses in net/netip","id":"CVE-2024-24790","kev_date_added":null,"published":"2024-06-05"},{"cvss_score":9.8,"headline":"Arbitrary code execution via go.mod toolchain directive in cmd/go","id":"CVE-2023-39320","kev_date_added":null,"published":"2023-09-08"},{"cvss_score":9.8,"headline":"Improper handling of JavaScript whitespace in html/template","id":"CVE-2023-24540","kev_date_added":null,"published":"2023-05-11"},{"cvss_score":9.8,"headline":"Backticks not treated as string delimiters in html/template","id":"CVE-2023-24538","kev_date_added":null,"published":"2023-04-06"},{"cvss_score":9.8,"headline":"Other in go/golang","id":"CVE-2012-2666","kev_date_added":null,"published":"2021-07-09"}],"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":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2025-02-13","vendors":["Go toolchain"]},"summary":"The Go toolchain may use insecure git protocols when fetching modules directly, bypassing security checks if the module proxy is disabled.","url":"https://insights.sbomify.com/CVE-2023-45285/"}