PT-2025-30162 · Go · Github.Com/Edgelesssys/Contrast
Publicado
2025-07-09
·
Atualizado
2025-07-09
CVSS v3.1
3.5
Baixa
| Vetor | AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N |
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.Correção
Files Accessible to External Parties
Protection Mechanism Failure
Encontrou algum problema na descrição? Tem algo a acrescentar? Fique à vontade para nos escrever 👾
Identificadores relacionados
Produtos afetados
Github.Com/Edgelesssys/Contrast