chainguard.dev/apko vulnerabilities
- Registry
- Go
- Latest
- 1.5.1
17 known advisories
The latest version, 1.5.1, is not affected by any of them. Projects on older versions may be.
go get chainguard.dev/apko@v1.5.1Is your project on an affected chainguard.dev/apko?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for chainguard.dev/apko
melange: Incomplete package integrity verification allows data section substitution in chainguard.dev/apko
- Affected
- <1.2.9
- Fixed in
- 1.2.9
melange: Incomplete package integrity verification allows data section substitution
- Affected
- <1.2.9
- Fixed in
- 1.2.9
apko dirFS has a symlink-following path traversal that allows multiple entry points to escape the build root in chainguard.dev/apko
- Affected
- >=0.14.8 <1.2.5
- Fixed in
- 1.2.5
apko doesn't verify downloaded apk packages against APKINDEX checksum (package substitution possible) in chainguard.dev/apko
- Affected
- <1.2.7
- Fixed in
- 1.2.7
apko `DiscoverKeys` has a panic on non-rsa jwks key that causes crash during key discovery in chainguard.dev/apko
- Affected
- <1.2.7
- Fixed in
- 1.2.7
apko doesn't verify downloaded apk packages against APKINDEX checksum (package substitution possible)
- Affected
- <1.2.7
- Fixed in
- 1.2.7
apko dirFS has a symlink-following path traversal that allows multiple entry points to escape the build root
- Affected
- >=0.14.8 <1.2.5
- Fixed in
- 1.2.5
apko `DiscoverKeys` has a panic on non-rsa jwks key that causes crash during key discovery
- Affected
- <1.2.7
- Fixed in
- 1.2.7
apko affected by potential unbounded resource consumption in expandapk.ExpandApk on attacker-controlled .apk streams in chainguard.dev/apko
- Affected
- >=0.14.8 <1.1.1
- Fixed in
- 1.1.1
apko has a path traversal in apko dirFS which allows filesystem writes outside base in chainguard.dev/apko
- Affected
- >=0.14.8 <1.1.0
- Fixed in
- 1.1.0
apko affected by unbounded resource consumption in expandapk.Split on attacker-controlled .apk streams in chainguard.dev/apko
- Affected
- >=0.14.8 <1.1.0
- Fixed in
- 1.1.0
apko affected by unbounded resource consumption in expandapk.Split on attacker-controlled .apk streams
- Affected
- >=0.14.8 <1.1.0
- Fixed in
- 1.1.0
apko has a path traversal in apko dirFS which allows filesystem writes outside base
- Affected
- >=0.14.8 <1.1.0
- Fixed in
- 1.1.0
apko is vulnerable to attack through incorrect permissions in /etc/ld.so.cache and other files in chainguard.dev/apko
- Affected
- >=0.27.0 <0.29.5
- Fixed in
- 0.29.5
apko is vulnerable to attack through incorrect permissions in /etc/ld.so.cache and other files
- Affected
- >=0.27.0 <0.29.5
- Fixed in
- 0.29.5
apko Exposure of HTTP basic auth credentials in log output in chainguard.dev/apko
- Affected
- <0.14.5
- Fixed in
- 0.14.5
apko Exposure of HTTP basic auth credentials in log output
- Affected
- <0.14.5
- Fixed in
- 0.14.5
Is your chainguard.dev/apko version vulnerable?
- chainguard.dev/apko 1.5No known advisories in 1.5.1
- chainguard.dev/apko 1.4No known advisories in 1.4.18
- chainguard.dev/apko 1.3No known advisories in 1.3.1
- chainguard.dev/apko 1.2No known advisories in 1.2.45
- chainguard.dev/apko 1.18 advisories in 1.1.16
- chainguard.dev/apko 1.013 advisories in 1.0.5
- chainguard.dev/apko 0.3013 advisories in 0.30.35
- chainguard.dev/apko 0.2913 advisories in 0.29.10
- chainguard.dev/apko 0.2815 advisories in 0.28.0
- chainguard.dev/apko 0.2715 advisories in 0.27.9
- chainguard.dev/apko 0.2613 advisories in 0.26.1
- chainguard.dev/apko 0.2513 advisories in 0.25.7
Which of your client projects still run an old chainguard.dev/apko?
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.