NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2024-23840: `goreleaser release --debug` shows secrets

mediumCVSS 3.1 5.5GHSA-h3q2-8whx-c29h

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 - run goreleaser release --debug You should see your secret value in the gorelease log. The log shows also the GITHUBTOKEN Example:

Published Jan 30, 2024

Affected packages

github.com/goreleaser/goreleaser

Ecosystem
Go
Affected
= 1.23.0
Fixed in
1.24.0
Check
go list -m github.com/goreleaser/goreleaser

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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

Credited to andreaangiolillo, caarlos0.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries