Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2005-0595: Buffer Overflow in BadBlue 2.55 ext.dll

Published Mar 1, 2005 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v2
EPSS60.1%99th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Working Resources Inc.
IdentifiersCVE-2005-0595CWE-120

A buffer overflow vulnerability exists in ext.dll in BadBlue 2.55. The vulnerability is triggered when a remote attacker sends a specially crafted request with an overly long mfcisapicommand parameter, causing a buffer overflow and allowing the execution of arbitrary code.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to execute arbitrary code with the privileges of the BadBlue process, potentially leading to full system compromise.

Mitigation

If you can’t patch tonight, do this now.

Restrict network access to the BadBlue service, use network-level filtering to block malicious requests, and monitor for suspicious activity targeting the mfcisapicommand parameter.

Remediation

Patch, then assume compromise.

Upgrade to a patched version of BadBlue that addresses the buffer overflow in ext.dll. If no patch is available, consider disabling or restricting access to the vulnerable component.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Working Resources Inc.Badblueapplication
FAQ

Frequently asked questions

Is CVE-2005-0595 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2005-0595 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2005-0595?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2005-0595, the earliest disclosed Apr 20, 2003.
Is there a patch for CVE-2005-0595?
Upgrade to a patched version of BadBlue that addresses the buffer overflow in ext.dll. If no patch is available, consider disabling or restricting access to the vulnerable component.
What products are affected by CVE-2005-0595?
Working Resources Inc. Badblue.
How severe is CVE-2005-0595?
CVE-2005-0595 has a CVSS v2 score of 7.5 (High) and an EPSS score of 60.1% (99th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.