github.com/sigstore/cosign vulnerabilities
- Registry
- Go
- Latest
- 1.13.6
17 known advisories
The latest version, 1.13.6, is affected by 10 of them.
Is your project on an affected github.com/sigstore/cosign?
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/cosign
Cosign's verify-blob-attestation reports false positive when payload parsing fails in github.com/sigstore/cosign
- Affected
- All versions
- Fixed in
- No fix released
Cosign's verify-blob-attestation reports false positive when payload parsing fails
- Affected
- <=1.13.6
- Fixed in
- No fix released
Cosign considered signatures valid with expired intermediate certificates when transparency log verification is skipped in github.com/sigstore/cosign
- Affected
- All versions
- Fixed in
- No fix released
Cosign considered signatures valid with expired intermediate certificates when transparency log verification is skipped
- Affected
- <3.0.5
- Fixed in
- 3.0.5
Cosign verification accepts any valid Rekor entry under certain conditions in github.com/sigstore/cosign
- Affected
- All versions
- Fixed in
- No fix released
Cosign malicious attachments can cause system-wide denial of service in github.com/sigstore/cosign
- Affected
- All versions
- Fixed in
- No fix released
Cosign malicious artifacts can cause machine-wide DoS in github.com/sigstore/cosign
- Affected
- All versions
- Fixed in
- No fix released
Cosign malicious artifacts can cause machine-wide DoS
- Affected
- <=2.2.3
- Fixed in
- No fix released
Cosign malicious attachments can cause system-wide denial of service
- Affected
- <=2.2.3
- Fixed in
- No fix released
Improper blob verification in github.com/sigstore/cosign
- Affected
- <1.12.0
- Fixed in
- 1.12.0
Denial of service attack from remote registry in github.com/sigstore/cosign
- Affected
- All versions
- Fixed in
- No fix released
Improper certificate validation in github.com/sigstore/cosign
- Affected
- <1.5.2
- Fixed in
- 1.5.2
Improper verification of signature attestations in github.com/sigstore/cosign
- Affected
- <1.10.1
- Fixed in
- 1.10.1
Cosign vulnerable to possible endless data attack from attacker-controlled registry
- Affected
- <1.13.2
- Fixed in
- 1.13.2
Cosign bundle can be crafted to successfully verify a blob even if the embedded rekorBundle does not reference the given signature
- Affected
- <1.12.0
- Fixed in
- 1.12.0
cosign's `cosign verify-attestaton --type` can report a false positive if any attestation exists
- Affected
- <1.10.1
- Fixed in
- 1.10.1
Improper Certificate Validation in Cosign
- Affected
- <1.5.2
- Fixed in
- 1.5.2
Is your github.com/sigstore/cosign version vulnerable?
- github.com/sigstore/cosign 1.1310 advisories in 1.13.6
- github.com/sigstore/cosign 1.1211 advisories in 1.12.1
- github.com/sigstore/cosign 1.1113 advisories in 1.11.1
- github.com/sigstore/cosign 1.1013 advisories in 1.10.1
- github.com/sigstore/cosign 1.915 advisories in 1.9.0
- github.com/sigstore/cosign 1.815 advisories in 1.8.0
- github.com/sigstore/cosign 0.617 advisories in 0.6.0
- github.com/sigstore/cosign 0.517 advisories in 0.5.0
- github.com/sigstore/cosign 0.417 advisories in 0.4.0
- github.com/sigstore/cosign 0.317 advisories in 0.3.1
- github.com/sigstore/cosign 0.217 advisories in 0.2.0
- github.com/sigstore/cosign 0.117 advisories in 0.1.0
Which of your client projects still run an old github.com/sigstore/cosign?
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.