{"answers":{"affected":"3 open source packages ship an affected version, including github.com/goreleaser/goreleaser.","exploited":"There is no known exploitation of GHSA-f6mm-5fc7-3g3c in the wild and no public exploit code.","fix":"Upgrade github.com/goreleaser/goreleaser to 1.26.1 or later.","what":"GHSA-f6mm-5fc7-3g3c is a vulnerability in github.com/goreleaser/goreleaser, published on 15 May 2024. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-f6mm-5fc7-3g3c and fix it if it is affected.\n\nWhat it is: GHSA-f6mm-5fc7-3g3c is a vulnerability in github.com/goreleaser/goreleaser, published on 15 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-f6mm-5fc7-3g3c in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/goreleaser/goreleaser (Go): affected from 1.26.0; fixed in 1.26.1\n- github.com/goreleaser/goreleaser (Go): affected from 1.26.0; fixed in 1.26.1\n- github.com/goreleaser/goreleaser (Go): affected from 1.26.0; fixed in 1.26.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/GHSA-f6mm-5fc7-3g3c/ (Markdown: https://insights.sbomify.com/GHSA-f6mm-5fc7-3g3c/index.md)","id":"GHSA-f6mm-5fc7-3g3c","markdown":"https://insights.sbomify.com/GHSA-f6mm-5fc7-3g3c/index.md","name":"GHSA-f6mm-5fc7-3g3c","record":{"aliases":["GO-2024-2860"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Go release tool","requires_auth":"none","summary":"Goreleaser leaks environment variables containing secrets in log output when Go build commands produce non-empty output.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Summary\nSince #4787 the log output is printed on the INFO level, while previously it was logged on DEBUG. This means if the `go build` output is non-empty, goreleaser leaks the environment.\n\n### PoC\n* Create a Go project with dependencies, do not pull them yet (or run goreleaser later in a container, or delete `$GOPATH/pkg`).\n* Make sure to have secrets set in the environment\n* Make sure to not have `go mod tidy` in a before hook\n* Run `goreleaser release --clean`\n* Go prints lots of `go: downloading ...` lines, which triggers the \"if output not empty, log it\" line, which includes the environment.\n\n### Impact\nCredentials and tokens are leaked.","ecosystems":["Go"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"goreleaser shows environment by default","id":"GHSA-f6mm-5fc7-3g3c","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Go","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":3,"n_references":null,"packages":[{"ecosystem":"Go","fixed":["1.26.1"],"introduced":["1.26.0"],"last_affected":[],"package":"github.com/goreleaser/goreleaser","purl":null,"source":"GHSA-f6mm-5fc7-3g3c"},{"ecosystem":"Go","fixed":["1.26.1"],"introduced":["1.26.0"],"last_affected":[],"package":"github.com/goreleaser/goreleaser","purl":"pkg:golang/github.com/goreleaser/goreleaser","source":"GHSA-f6mm-5fc7-3g3c"},{"ecosystem":"Go","fixed":["1.26.1"],"introduced":["1.26.0"],"last_affected":[],"package":"github.com/goreleaser/goreleaser","purl":"pkg:golang/github.com/goreleaser/goreleaser","source":"GO-2024-2860"}],"products":null,"published":"2024-05-15","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Goreleaser leaks environment variables containing secrets in log output when Go build commands produce non-empty output.","url":"https://insights.sbomify.com/GHSA-f6mm-5fc7-3g3c/"}