Khaled Mardam-Bey mIRC up to 5.91 Nickname memory corruption

Summaryinfo

A vulnerability was found in Khaled Mardam-Bey mIRC. It has been rated as critical. This impacts an unknown function of the component Nickname Handler. The manipulation leads to memory corruption. This vulnerability is uniquely identified as CVE-2002-0231. Moreover, an exploit is present.

Detailsinfo

A vulnerability, which was classified as critical, has been found in Khaled Mardam-Bey mIRC (Chat Software). This issue affects an unknown function of the component Nickname Handler. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Buffer overflow in mIRC 5.91 and earlier allows a remote server to execute arbitrary code on the client via a long nickname.

The weakness was disclosed 05/16/2002 by Martin (Website). The advisory is shared at marc.theaimsgroup.com. The identification of this vulnerability is CVE-2002-0231. 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 unknown but a public exploit is available.

A public exploit has been developed in ANSI C. The exploit is available at securityfocus.com. It is declared as proof-of-concept.

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 databases at X-Force (8083), Exploit-DB (21274) and SecurityFocus (BID 4027†). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• Chat Software

Vendor

• Khaled Mardam-Bey

Name

• mIRC

Version

• 2.1a
• 2.3a
• 2.4
• 2.4a
• 2.5a
• 2.7a
• 2.8c
• 3.1
• 3.2
• 3.3
• 3.4
• 3.5
• 3.6
• 3.7
• 3.8
• 3.9
• 4.0
• 4.1
• 4.5
• 4.6
• 4.7
• 5.0
• 5.1
• 5.3
• 5.4
• 5.5
• 5.6
• 5.7
• 5.8
• 5.9
• 5.91

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