github.com/sigstore/rekor vulnerabilities
- Registry
- Go
- Latest
- 1.6.1
10 known advisories
The latest version, 1.6.1, is not affected by any of them. Projects on older versions may be.
go get github.com/sigstore/rekor@v1.6.1Is your project on an affected github.com/sigstore/rekor?
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/rekor
Rekor has an OOM Condition due to Unbounded gzip Decompression in Alpine APK Parsing Logic in github.com/sigstore/rekor
- Affected
- >=0.3.0 <1.5.2
- Fixed in
- 1.5.2
Rekor has an OOM Condition due to Unbounded gzip Decompression in Alpine APK Parsing Logic
- Affected
- >=0.3.0 <1.5.2
- Fixed in
- 1.5.2
Rekor's COSE v0.0.1 entry type nil pointer dereference in Canonicalize via empty Message in github.com/sigstore/rekor
- Affected
- <1.5.0
- Fixed in
- 1.5.0
Rekor affected by Server-Side Request Forgery (SSRF) via provided public key URL in github.com/sigstore/rekor
- Affected
- <1.5.0
- Fixed in
- 1.5.0
Rekor affected by Server-Side Request Forgery (SSRF) via provided public key URL
- Affected
- <1.5.0
- Fixed in
- 1.5.0
Rekor's COSE v0.0.1 entry type nil pointer dereference in Canonicalize via empty Message
- Affected
- <1.5.0
- Fixed in
- 1.5.0
malformed proposed intoto entries can cause a panic in github.com/sigstore/rekor
- Affected
- <1.2.0
- Fixed in
- 1.2.0
Rekor's compressed archives can result in OOM conditions in github.com/sigstore/rekor
- Affected
- <1.1.1
- Fixed in
- 1.1.1
malformed proposed intoto entries can cause a panic
- Affected
- <1.2.0
- Fixed in
- 1.2.0
Rekor's compressed archives can result in OOM conditions
- Affected
- <1.1.1
- Fixed in
- 1.1.1
Is your github.com/sigstore/rekor version vulnerable?
- github.com/sigstore/rekor 1.6No known advisories in 1.6.1
- github.com/sigstore/rekor 1.5No known advisories in 1.5.6
- github.com/sigstore/rekor 1.46 advisories in 1.4.3
- github.com/sigstore/rekor 1.36 advisories in 1.3.10
- github.com/sigstore/rekor 1.26 advisories in 1.2.2
- github.com/sigstore/rekor 1.18 advisories in 1.1.1
- github.com/sigstore/rekor 0.1210 advisories in 0.12.2
- github.com/sigstore/rekor 0.1110 advisories in 0.11.0
- github.com/sigstore/rekor 0.1010 advisories in 0.10.0
- github.com/sigstore/rekor 0.910 advisories in 0.9.1
- github.com/sigstore/rekor 0.810 advisories in 0.8.2
- github.com/sigstore/rekor 0.710 advisories in 0.7.0
Which of your client projects still run an old github.com/sigstore/rekor?
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.