Microsoft Terminal Server Client Connection Manager memory corruption ⚔ [Disputed]

Summaryinfo

A vulnerability categorized as critical has been discovered in Microsoft Terminal Server. Impacted is an unknown function of the component Client Connection Manager. Executing a manipulation can lead to memory corruption. This vulnerability is handled as CVE-2006-4465. There is not any exploit available. The actual existence of this vulnerability is currently in question.

Detailsinfo

A vulnerability has been found in Microsoft Terminal Server (affected version unknown) and classified as very critical. This vulnerability affects an unknown functionality of the component Client Connection Manager. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

** DISPUTED ** Microsoft Terminal Server, when running an application session with the "Start program at logon" and "Override settings from user profile and Client Connection Manager wizard" options, allows local users to execute arbitrary code by forcing an Explorer error. NOTE: a third-party researcher has stated that the options are "a convenience to users" and were not intended to restrict execution of arbitrary code.

The weakness was released 08/31/2006 as not defined posting (Bugtraq). The advisory is available at securityfocus.com. This vulnerability was named CVE-2006-4465 since 08/31/2006. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. The technical details are unknown and an exploit is not available. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 08/08/2024).

The real existence of this vulnerability is still doubted at the moment.

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

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• Microsoft

Name

• Terminal Server

License

• commercial

Website

• Vendor: https://www.microsoft.com/

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion