A malicious BuildKit frontend or Dockerfile using RUN --mount
could trick the feature that removes empty files created for the mountpoints into removing a file outside the container, from the host system.
The issue has been fixed in v0.12.5
Avoid using BuildKit frontend from an untrusted source or building an untrusted Dockerfile containing RUN --mount
feature.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
3.9
Package | Type | OS Name | OS Version | Affected Ranges | Fix Versions |
---|---|---|---|---|---|
github.com/moby/buildkit | golang | - | - | <0.12.5 | 0.12.5 |
github.com/moby/buildkit | golang | - | - | <0.0.0-20240131194315-bac3f2b673f3 | 0.0.0-20240131194315-bac3f2b673f3 |
CVSS:3 Severity and metrics
The CVSS metrics represent various qualitative aspects of a vulnerability that influence the overall score above.
Attack Vector (AV)
Network
The vulnerable component is bound to the network stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared physical (e.g., Bluetooth or IEEE 802.11) or logical (e.g., local IP subnet) network, or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN to an administrative network zone). One example of an Adjacent attack would be an ARP (IPv4) or neighbor discovery (IPv6) flood leading to a denial of service on the local LAN segment (e.g., CVE-2013-6014).
Attack Complexity (AC)
Low
Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.
Privileges Required (PR)
None
The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction (UI)
None
The vulnerable system can be exploited without interaction from any user.
Scope (S)
Changed
An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality (C)
None
There is no loss of confidentiality.
Integrity (I)
High
There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any or all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability (A)
High
There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component.
3.9
-
3.9
-
-
1.0
CGA-2cv7-75q6-cvrq
-
CGA-4v29-m22x-5m58
-
CGA-7vxc-hp2w-725j
-
CGA-7wr2-gxv6-5g96
-
CGA-9rhv-6x5x-p3wh
-
CGA-cf38-mj9p-m2h7
-
CGA-hqhv-f77r-cq7c
-
CGA-jh3p-vg64-hm2m
-
CGA-m737-5xv8-m883
-
CGA-mp67-g995-65f4
-
CGA-rpw2-9v92-4g7f
-
CGA-wgv3-9hrx-gj3g
-
CGA-x5pw-xwxw-p7jx
-