Two malicious build steps running in parallel sharing the same cache mounts with subpaths could cause a race condition that can lead to files from the host system being accessible to the build container.
The issue has been fixed in v0.12.5
Avoid using BuildKit frontend from an untrusted source or building an untrusted Dockerfile containing cache mounts with --mount=type=cache,source=...
options.
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
2.2
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)
High
A successful attack depends on conditions beyond the attacker's control, requiring investing a measurable amount of effort in research, preparation, or execution against the vulnerable component before a successful attack.
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)
High
There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
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)
None
There is no impact to availability within the impacted component.
2.2
-
2.2
-
-
1.1
CGA-2pf6-mcw3-86w8
-
CGA-35v4-4g89-c7vg
-
CGA-5r59-v4x3-mcq8
-
CGA-7x8v-47c7-r9j5
-
CGA-8v8h-vjwp-w2q2
-
CGA-9qpq-5hvj-539p
-
CGA-cfmq-73h4-8888
-
CGA-hpfp-4ff7-27r4
-
CGA-m4g3-g2h3-p3rq
-
CGA-v5x3-4vp7-q26m
-
CGA-rgpg-f9fq-2pv5
-
CGA-wmg5-h8w8-cvgm
-
CGA-xv2h-pv92-v4rc
-