malcontent's OCI image scanning could expose registry credentials
chainguard-dev malcontent
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/chainguard-dev/malcontent Go |
|
|
| github.com/chainguard-dev/bincapz Go |
| No fix yet |
chainguard-dev malcontent
| Product | Affected | Fixed in |
|---|---|---|
| github.com/chainguard-dev/malcontent Go |
|
|
| github.com/chainguard-dev/bincapz Go |
| No fix yet |
malcontent discovers supply-chain compromises through. context, differential analysis, and YARA. Starting in version 0.10.0 and prior to version 1.20.3, malcontent could be made to expose Docker registry credentials if it scanned a specially crafted OCI image reference. malcontent uses google/go-containerregistry for OCI image pulls, which by default uses the Docker credential keychain. A malicious registry could return a `WWW-Authenticate` header redirecting token authentication to an attacker-controlled endpoint, causing credentials to be sent to that endpoint. Version 1.20.3 fixes the issue by defaulting to anonymous auth for OCI pulls.
From the CVE record · GitHub_M
malcontent before 1.20.3 can expose Docker registry credentials when it scans a specially crafted OCI image reference. A malicious registry can redirect token authentication to an attacker-controlled endpoint, causing credentials to be sent there. The scan must be initiated; the input does not specify an authentication requirement for the attacker.
Check deployments using Go package github.com/chainguard-dev/malcontent from 0.10.0 through versions before 1.20.3, or github.com/chainguard-dev/bincapz version 0.10.0 or later.