github.com/sigstore/gitsign vulnerabilities
- Registry
- Go
- Latest
- 0.18.0
8 known advisories
The latest version, 0.18.0, is not affected by any of them. Projects on older versions may be.
go get github.com/sigstore/gitsign@v0.18.0Is your project on an affected github.com/sigstore/gitsign?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for github.com/sigstore/gitsign
gitsign --verify panics on empty-certificate PKCS7 and exits 0, bypassing exit-code callers in github.com/sigstore/gitsign
- Affected
- >=0.4.0 <0.15.0
- Fixed in
- 0.15.0
gitsign verify accepts signatures over go-git-normalized bytes, enabling trust confusion on malformed commits in github.com/sigstore/gitsign
- Affected
- <0.16.0
- Fixed in
- 0.16.0
gitsign verify accepts signatures over go-git-normalized bytes, enabling trust confusion on malformed commits
- Affected
- <0.16.0
- Fixed in
- 0.16.0
gitsign --verify panics on empty-certificate PKCS7 and exits 0, bypassing exit-code callers
- Affected
- >=0.4.0 <0.15.0
- Fixed in
- 0.15.0
gitsign may use incorrect Rekor entries during verification in github.com/sigstore/gitsign
- Affected
- <0.11.0
- Fixed in
- 0.11.0
gitsign may use incorrect Rekor entries during verification
- Affected
- <0.11.0
- Fixed in
- 0.11.0
Gitsign's Rekor public keys fetched from upstream API instead of local TUF client. in github.com/sigstore/gitsign
- Affected
- >=0.6.0 <0.8.0
- Fixed in
- 0.8.0
Gitsign's Rekor public keys fetched from upstream API instead of local TUF client.
- Affected
- >=0.6.0 <0.8.0
- Fixed in
- 0.8.0
Is your github.com/sigstore/gitsign version vulnerable?
- github.com/sigstore/gitsign 0.18No known advisories in 0.18.0
- github.com/sigstore/gitsign 0.17No known advisories in 0.17.1
- github.com/sigstore/gitsign 0.16No known advisories in 0.16.1
- github.com/sigstore/gitsign 0.152 advisories in 0.15.1
- github.com/sigstore/gitsign 0.144 advisories in 0.14.0
- github.com/sigstore/gitsign 0.134 advisories in 0.13.0
Which of your client projects still run an old github.com/sigstore/gitsign?
NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Go packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.