`goreleaser release --debug` shows secrets
cve-program · CVE-2024-23840
PublishedGoReleaser builds Go binaries for several platforms, creates a GitHub release and then pushes a Homebrew formula to a tap repository. `goreleaser release --debug` log shows secret values used in the in the custom publisher. This vulnerability is fixed in 1.24.0.
Read the publisher's advisoryeuvd · EUVD-2024-0363
PublishedGoReleaser builds Go binaries for several platforms, creates a GitHub release and then pushes a Homebrew formula to a tap repository. `goreleaser release --debug` log shows secret values used in the in the custom publisher. This vulnerability is fixed in 1.24.0.
Read the publisher's advisorynvd · CVE-2024-23840
PublishedGoReleaser builds Go binaries for several platforms, creates a GitHub release and then pushes a Homebrew formula to a tap repository. `goreleaser release --debug` log shows secret values used in the in the custom publisher. This vulnerability is fixed in 1.24.0.
Read the publisher's advisoryosv · GHSA-h3q2-8whx-c29h
Published### Summary Hello 👋 `goreleaser release --debug` log shows secret values used in the in the custom publisher. How to reproduce the issue: - Define a custom publisher as the one below. Make sure to provide a custom script to the `cmd` field and to provide a secret to `env` ``` #.goreleaser.yml publishers: - name: my-publisher # IDs of the artifacts we want to sign ids: - linux_archives - linux_package cmd: "./build/package/linux_notarize.sh" env: - VERSION={{ .Version }} - SECRET_1={{.Env.SECRET_1}} - SECRET_2={{.Env.SECRET_2}} ``` - run `goreleaser release --debug` You should see your secret value in the gorelease log. The log shows also the `GITHUB_TOKEN` Example: ``` running cmd= .... SECRET_1=secret_value ```
Read the publisher's advisoryosv · GO-2024-2482
PublishedSecret values can be printed to the --debug log when using a a custom publisher.
Read the publisher's advisoryAffected versions, risk and source history
Related advisories and sources
Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.
CVE-2024-23840 · CVE overview and exploitation status
cve-program · CVE-2024-23840
- https://github.com/goreleaser/goreleaser/security/advisories/GHSA-h3q2-8whx-c29h
- https://github.com/goreleaser/goreleaser/commit/d5b6a533ca1dc3366983d5d31ee2d2b6232b83c0
euvd · EUVD-2024-0363
- https://github.com/goreleaser/goreleaser/security/advisories/GHSA-h3q2-8whx-c29h
- https://github.com/goreleaser/goreleaser/commit/d5b6a533ca1dc3366983d5d31ee2d2b6232b83c0
nvd · CVE-2024-23840
- https://github.com/goreleaser/goreleaser/commit/d5b6a533ca1dc3366983d5d31ee2d2b6232b83c0
- https://github.com/goreleaser/goreleaser/security/advisories/GHSA-h3q2-8whx-c29h
osv · GHSA-h3q2-8whx-c29h
- https://github.com/goreleaser/goreleaser/security/advisories/GHSA-h3q2-8whx-c29h
- https://nvd.nist.gov/vuln/detail/CVE-2024-23840
- https://github.com/goreleaser/goreleaser/commit/d5b6a533ca1dc3366983d5d31ee2d2b6232b83c0
- https://github.com/goreleaser/goreleaser
osv · GO-2024-2482
Related changes
Linked by CVE identifierNo related changes are available here.