compose-spec compose-go up to 2.4.0 YAML input validation

Summaryinfo

A vulnerability identified as problematic has been detected in compose-spec compose-go up to 2.4.0. This affects an unknown part of the component YAML Handler. The manipulation leads to input validation. This vulnerability is documented as CVE-2024-10846. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in compose-spec compose-go up to 2.4.0. This issue affects some unknown functionality of the component YAML Handler. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Impacted is availability. The summary by CVE is:

The compose-go library component in versions v2.10-v2.4.0 allows an authorized user who sends malicious YAML payloads to cause the compose-go to consume excessive amount of Memory and CPU cycles while parsing YAML, such as used by Docker Compose from versions v2.27.0 to v2.29.7 included

The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-10846 since 11/05/2024. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/26/2025).

The vulnerability scanner Nessus provides a plugin with the ID 216199 (SUSE SLES15 / openSUSE 15 Security Update : govulncheck-vulndb (SUSE-SU-2025:0429-1)), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Tenable (216199). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• compose-spec

Name

• compose-go

Version

• 2.0
• 2.1
• 2.2
• 2.3
• 2.4.0

Website

• Product: https://github.com/compose-spec/compose-go/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion