Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

`goreleaser release --debug` shows secrets

CVSS 3.1 5.5 MEDIUMEUVD CVSS 3.1 5.5 CVSS 3.1 · [email protected] · Secondary 5.5 MEDIUMCVSS 3.1 · [email protected] · Primary 5.5 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by github.com/goreleaser/goreleaser 1.24.0osv · severity unknownFixed by github.com/goreleaser/goreleaser 1.24.0KEV status unknown

cve-program · CVE-2024-23840

Published

GoReleaser 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 advisory

euvd · EUVD-2024-0363

Published

GoReleaser 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 advisory

nvd · CVE-2024-23840

Published

GoReleaser 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 advisory

osv · 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 advisory

osv · GO-2024-2482

Published

Secret values can be printed to the --debug log when using a a custom publisher.

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Related changes

Linked by CVE identifier

No related changes are available here.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 17:03 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current