Skip to main content
Mallory
MediumVulnerability

CVE-2006-1194: DoS in ENet protocol.c enet_protocol_handle_incoming_commands via signedness error

Published Mar 13, 2006 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.0Medium · v2
EPSS4.4%92nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Enet
IdentifiersCVE-2006-1194CWE-195

CVE-2006-1194 is an integer signedness error in the ENet networking library (CVS Jul 2005 and earlier) within the function enet_protocol_handle_incoming_commands in protocol.c. A remote attacker can send a crafted network packet containing an excessively large command length value that is mishandled due to signed/unsigned interpretation, resulting in an invalid memory access and application crash. The issue affects ENet as used by products including Cube, Sauerbraten, and Duke3d_w32.

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.

Remote, unauthenticated denial of service: an attacker can crash the affected application by triggering an invalid memory access via a crafted packet with a large command length value.

Mitigation

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

Until patched, reduce exposure by restricting network access to the affected service to trusted sources (e.g., firewall/ACLs, VPN-only access) and monitor for anomalous or malformed traffic indicative of crafted packets targeting command length handling.

Remediation

Patch, then assume compromise.

Upgrade ENet to a version released after July 2005 (or otherwise patched) that corrects the signedness handling in protocol.c / enet_protocol_handle_incoming_commands, and rebuild/redeploy dependent applications (e.g., Cube, Sauerbraten, Duke3d_w32) against the fixed library.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
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
EnetEnet Libraryapplication
FAQ

Frequently asked questions

Is CVE-2006-1194 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2006-1194 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2006-1194?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2006-1194. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2006-1194?
Upgrade ENet to a version released after July 2005 (or otherwise patched) that corrects the signedness handling in protocol.c / enet_protocol_handle_incoming_commands, and rebuild/redeploy dependent applications (e.g., Cube, Sauerbraten, Duke3d_w32) against the fixed library.
What products are affected by CVE-2006-1194?
Enet Library.
How severe is CVE-2006-1194?
CVE-2006-1194 has a CVSS v2 score of 5.0 (Medium) and an EPSS score of 4.4% (92nd 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.