moby buildkit up to 0.12.4 API authorization

Summaryinfo

A vulnerability identified as very critical has been detected in moby buildkit up to 0.12.4. Affected by this vulnerability is an unknown functionality of the component API. The manipulation leads to authorization. This vulnerability is uniquely identified as CVE-2024-23653. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in moby buildkit up to 0.12.4 and classified as very critical. This issue affects some unknown functionality of the component API. The manipulation with an unknown input leads to a authorization vulnerability. Using CWE to declare the problem leads to CWE-863. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows attackers to bypass intended access restrictions. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

BuildKit is a toolkit for converting source code to build artifacts in an efficient, expressive and repeatable manner. In addition to running containers as build steps, BuildKit also provides APIs for running interactive containers based on built images. It was possible to use these APIs to ask BuildKit to run a container with elevated privileges. Normally, running such containers is only allowed if special `security.insecure` entitlement is enabled both by buildkitd configuration and allowed by the user initializing the build request. The issue has been fixed in v0.12.5 . Avoid using BuildKit frontends from untrusted sources.

The weakness was disclosed 02/01/2024 as GHSA-wr6v-9f75-vh2g. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2024-23653 since 01/19/2024. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/01/2024).

Upgrading to version 0.12.5 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Vendor

• moby

Name

• buildkit

Version

• 0.12.0
• 0.12.1
• 0.12.2
• 0.12.3
• 0.12.4

Website

• Product: https://github.com/moby/buildkit/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion