QEMU 3.0.0 qga/commands*.c Environment Variable integer overflow ⚔ [Disputed]

Summaryinfo

A vulnerability has been found in QEMU 3.0.0 and classified as critical. This affects an unknown part of the file qga/commands*.c. This manipulation as part of Environment Variable causes integer overflow. This vulnerability appears as CVE-2019-12247. The attack may be initiated remotely. There is no available exploit. The presence of this vulnerability remains uncertain at this time.

Detailsinfo

A vulnerability was found in QEMU 3.0.0 (Virtualization Software). It has been declared as critical. Affected by this vulnerability is an unknown part of the file qga/commands*.c. The manipulation as part of a Environment Variable leads to a integer overflow vulnerability. The CWE definition for the vulnerability is CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

QEMU 3.0.0 has an Integer Overflow because the qga/commands*.c files do not check the length of the argument list or the number of environment variables.

The weakness was presented 05/22/2019 (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2019-12247 since 05/21/2019. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 03/07/2025).

The real existence of this vulnerability is still doubted at the moment. The vulnerability scanner Nessus provides a plugin with the ID 232058 (Linux Distros Unpatched Vulnerability : CVE-2019-12247), 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 (232058). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Virtualization Software

Name

• QEMU

Version

• 3.0.0

License

• open-source

Website

• Product: https://www.qemu.org/

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion