GHSA-phhq-63jg-fp7r: Contrast vulnerability allows arbitrary host data Injection into container VOLUME mount points
Background The VOLUME directive in Dockerfiles, or the config.volumes field in OCI image descriptors, indicates filesystem paths "where the process is likely to write data". While these paths have special semantics in Docker, they are only hints in the OCI spec and are not treated specially by Kubernetes.
Published Jul 9, 2025
Affected packages
github.com/edgelesssys/contrast
- Ecosystem
- Go
- Affected
- < 1.9.1
- Fixed in
- 1.9.1
- Check
go list -m github.com/edgelesssys/contrast
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Background
The `VOLUME` directive in Dockerfiles, or the `config.volumes` field in OCI image descriptors, indicates filesystem paths "where the process is likely to write data". While these paths have special semantics in Docker, they are only hints in the OCI spec and are not treated specially by Kubernetes. However, containered implements the specified conversion logic and adds a mount point if there is none set by Kubernetes.
Unfortunately, the specification leaves it open whether the mount point is populated with any and what data, so the runtime needs to be able to push arbitrary data to the Kata agent. However, this is almost always not what the user wants:
- A declared
VOLUMElocation is usually important to the app's core functionality, which is usually at odds with the data in that location being untrusted. VOLUMEdeclarations are often used by image vendors to indicate "mount your persistence here" to the user. They are rarely useful without a real volume mounted there.
Impact
All of the following need to be true to be affected by this vulnerability:
- A bare metal Contrast deployment (AKS is not affected).
- An image with at least one VOLUME directive.
- No Kubernetes mount at the path of the VOLUME.
If these are all true, the host is able to write arbitrary trees below that mount point.
Patches
Patched in v1.9.1 by disallowing this configuration in contrast generate.
Workarounds
Explicitly mount an emptyDir to all VOLUME locations. If the initial data in these locations is needed by the application, the image needs to be modified to remove the config.volumes entries.
Credited to burgerdev, katexochen, thomasten.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesGHSA-3ccm-4qq2-5wrp
Constrata's coordinator transit engine `ciphertextContainer.UnmarshalJSON` panics on attacker-controlled short ciphertexts
medium4.3Jul 1, 2026GHSA-6c87-g9pw-78fx
Contrast's Imagepuller registryFor uses unanchored suffix matching, leaking auth credentials and trusted CA configuration to sibling-domain registries
low3.7Jul 1, 2026GHSA-rh99-wc69-c255
Contras Affected by CopyFile Policy Subversion via Symlinks
high8.1Apr 30, 2026GHSA-g9ww-x58f-9g6m
Contrast BadAML injection allows arbitrary code execution
high8.4Mar 26, 2026GHSA-f5p4-p5q5-jv3h
Contrast has insecure LUKS2 persistent storage partitions may be opened and used
medium5.7Oct 28, 2025GHSA-vxg3-w9rv-rhr2
Contrast leaks workload secrets to logs on INFO level
high7.3Aug 28, 2025
