github.com/chainguard-dev/malcontent vulnerabilities
- Registry
- Go
- Latest
- 1.28.2
8 known advisories
The latest version, 1.28.2, is not affected by any of them. Projects on older versions may be.
go get github.com/chainguard-dev/malcontent@v1.28.2Is your project on an affected github.com/chainguard-dev/malcontent?
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/chainguard-dev/malcontent
malcontent: Nested archive extraction failure can drop content from scan inputs in github.com/chainguard-dev/malcontent
- Affected
- <1.21.0
- Fixed in
- 1.21.0
malcontent: Error-path cleanup gap can leak scanners and fds and degrade availability in github.com/chainguard-dev/malcontent
- Affected
- <1.21.0
- Fixed in
- 1.21.0
malcontent: Error-path cleanup gap can leak scanners and fds and degrade availability
- Affected
- <1.21.0
- Fixed in
- 1.21.0
malcontent: Nested archive extraction failure can drop content from scan inputs
- Affected
- <1.21.0
- Fixed in
- 1.21.0
malcontent OCI image pull credential exfiltration via malicious registry token realm in github.com/chainguard-dev/malcontent
- Affected
- <1.20.3
- Fixed in
- 1.20.3
malcontent vulnerable to symlink Path Traversal via handleSymlink argument confusion in archive extraction in github.com/chainguard-dev/malcontent
- Affected
- >=1.8.0 <1.20.3
- Fixed in
- 1.20.3
malcontent vulnerable to symlink Path Traversal via handleSymlink argument confusion in archive extraction
- Affected
- >=1.8.0 <1.20.3
- Fixed in
- 1.20.3
malcontent OCI image pull credential exfiltration via malicious registry token realm
- Affected
- >=0.10.0 <1.20.3
- Fixed in
- 1.20.3
Is your github.com/chainguard-dev/malcontent version vulnerable?
- github.com/chainguard-dev/malcontent 1.28No known advisories in 1.28.2
- github.com/chainguard-dev/malcontent 1.27No known advisories in 1.27.1
- github.com/chainguard-dev/malcontent 1.26No known advisories in 1.26.3
- github.com/chainguard-dev/malcontent 1.25No known advisories in 1.25.9
- github.com/chainguard-dev/malcontent 1.24No known advisories in 1.24.2
- github.com/chainguard-dev/malcontent 1.23No known advisories in 1.23.1
- github.com/chainguard-dev/malcontent 0.196 advisories in 0.19.0
- github.com/chainguard-dev/malcontent 0.186 advisories in 0.18.2
- github.com/chainguard-dev/malcontent 0.176 advisories in 0.17.1
- github.com/chainguard-dev/malcontent 0.166 advisories in 0.16.2
- github.com/chainguard-dev/malcontent 0.156 advisories in 0.15.1
- github.com/chainguard-dev/malcontent 0.146 advisories in 0.14.0
Which of your client projects still run an old github.com/chainguard-dev/malcontent?
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.