Advisory

GHSA-h3q2-8whx-c29h

Also known as: CVE-2024-23840, GO-2024-2482

Summary

goreleaser release --debug shows secrets

Details

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

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2024-01-30 20:57 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

github.com/goreleaser/goreleaser

Go · All systems

Affected

  • introduced 1.23.0, fixed 1.24.0 (semver)

Fixed versions

1.24.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences