melange: Incomplete package integrity verification allows data section substitution
chainguard-dev melange · chainguard-dev apko
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| chainguard.dev/apko Go |
|
|
| chainguard.dev/melange Go |
|
|
chainguard-dev melange · chainguard-dev apko
| Product | Affected | Fixed in |
|---|---|---|
| chainguard.dev/apko Go |
|
|
| chainguard.dev/melange Go |
|
|
melange allows users to build apk packages using declarative pipelines. Apko prior to version 1.2.9, corresponding to melange prior to version 0.50.4, verified the control section hash (`.PKGINFO` etc.) against the signed `APKINDEX`, but never verified the data section hash (the actual package files that get installed). An attacker who could compromise a mirror, poison a cache, or MITM a package fetch could substitute arbitrary file contents while the control hash check still passed. Apko version 1.2.9 and melange version 0.50.4 contain a fix.
From the CVE record · GitHub_M
Apko before 1.2.9, corresponding to melange before 0.50.4, checked an APK package's control section hash against the signed APKINDEX but did not check the data section hash. An attacker able to compromise a mirror, poison a cache, or intercept a package fetch could substitute arbitrary contents for files that get installed while the control hash check still passed.
Engineers using Go package chainguard.dev/apko before 1.2.9 or chainguard.dev/melange before 0.50.4 should check their deployments.