dbcve.org
Memory Buffer Bounds ErrorWeakness · CWE-119

CVE-2025-2401

MEDIUM · 5.4 CVSS v4.0 Published 2025-03-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
54/100
Remediation priority · Moderate

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Buffer overflow vulnerability in Immunity Debugger version 1.85 allows a local attacker to execute arbitrary code due to lack of proper boundary checking when processing input.

MitigationUntil an official patch is released, restrict access to systems running Immunity Debugger, avoid processing untrusted files with the tool, and monitor for unusual behavior.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
High
Privileges
Low
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Immunity Debugger installation
    Search the system for the Immunity Debugger executable (immunitydebugger.exe) using file search or check common installation directories such as C:\Program Files\Immunity Inc\Immunity Debugger or C:\Program Files (x86)\Immunity Inc\Immunity Debugger
    Affected if The executable is found on the system, indicating Immunity Debugger is installed
  2. Identify installed version
    Run Immunity Debugger and navigate to Help > About, or attempt to invoke the executable with a version flag if supported, to obtain the exact version number
    Affected if The installed version is 1.85, matching the affected version stated in the CVE
  3. Verify version against affected range
    Compare the identified version against the affected version range. Since only version 1.85 is explicitly listed as affected, any version other than 1.85 is not covered by this specific CVE
    Affected if The installed version is exactly 1.85, making it the only version explicitly affected by this CVE
  4. Determine if tool processes external input
    Assess whether Immunity Debugger is used to open, analyze, or debug files from untrusted sources such as downloaded executables, third-party binaries, or files from non-privileged users
    Affected if The tool is used to process input files from untrusted or external sources, as the vulnerability triggers during input processing
  5. Check local access exposure
    Evaluate whether untrusted local users or processes have the ability to supply input to Immunity Debugger or to invoke the tool with crafted arguments
    Affected if Local untrusted users or processes can interact with Immunity Debugger, enabling the buffer overflow attack vector

A system is affected if Immunity Debugger version 1.85 is installed and is used to process input files, particularly from untrusted sources, allowing a local attacker to trigger the buffer overflow.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Until an official patch is released, restrict access to systems running Immunity Debugger, avoid processing untrusted files with the tool, and monitor for unusual behavior.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-2401 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-2401 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data