| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/goreleaser/goreleaser | ≥ 1.23.0, < 1.24.0 | 1.24.0 |
| goreleaser | = 1.23.0 |
Hello 👋
goreleaser release --debug log shows secret values used in the in the custom publisher.
How to reproduce the issue:
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}}
goreleaser release --debugYou should see your secret value in the gorelease log. The log shows also the GITHUB_TOKEN
Example:
running cmd= ....
SECRET_1=secret_value
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free