Immunity Debugger 1.85 memory corruption

Summaryinfo

A vulnerability marked as critical has been reported in Immunity Debugger 1.85. Affected by this issue is some unknown functionality. This manipulation causes memory corruption. This vulnerability is registered as CVE-2025-2401. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in Immunity Debugger 1.85. It has been declared as critical. Affected by this vulnerability is an unknown code. 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. The summary by CVE is:

Buffer overflow vulnerability in Immunity Debugger affecting version 1.85, its exploitation could allow a local attacker to execute arbitrary code, due to the lack of proper boundary checking.

The weakness was published by Rafael Pedrero. The advisory is shared at incibe.es. This vulnerability is known as CVE-2025-2401 since 03/17/2025. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. 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 03/17/2025).

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

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

Productinfo

Vendor

• Immunity

Name

• Debugger

Version

• 1.85

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