LinuxVNC/VNCommand up to 0.9.10 VNConsole.c vcSetXCutTextProc integer overflow

Summaryinfo

A vulnerability, which was classified as critical, has been found in LinuxVNC and VNCommand up to 0.9.10. Affected by this vulnerability is the function vcSetXCutTextProc of the file VNConsole.c. The manipulation leads to integer overflow. This vulnerability is uniquely identified as CVE-2018-7226. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in LinuxVNC and VNCommand up to 0.9.10. It has been rated as critical. This issue affects the function vcSetXCutTextProc of the file VNConsole.c. The manipulation with an unknown input leads to a integer overflow vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

An issue was discovered in vcSetXCutTextProc() in VNConsole.c in LinuxVNC and VNCommand from the LibVNC/vncterm distribution through 0.9.10. Missing sanitization of the client-specified message length may cause integer overflow or possibly have unspecified other impact via a specially crafted VNC packet.

The bug was discovered 02/19/2018. The weakness was disclosed 02/19/2018 (Website). The advisory is shared at openwall.com. The identification of this vulnerability is CVE-2018-7226 since 02/19/2018. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 261373 (Linux Distros Unpatched Vulnerability : CVE-2018-7226), 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 (261373). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• LinuxVNC
• VNCommand

Version

• 0.9.0
• 0.9.1
• 0.9.2
• 0.9.3
• 0.9.4
• 0.9.5
• 0.9.6
• 0.9.7
• 0.9.8
• 0.9.9
• 0.9.10

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