CVE-2006-1195 json
The enet_protocol_handle_send_fragment function in protocol.c for ENet library CVS version Jul 2005 and earlier, as used in products includ…
published 2006-03-13 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-1199
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.4%
- EPSS 2.4% chance of exploitation in 30 days, percentile 83%
- public exploits
- 0
- none known
Summary
The enet_protocol_handle_send_fragment function in protocol.c for ENet library CVS version Jul 2005 and earlier, as used in products including (1) Cube, (2) Sauerbraten, and (3) Duke3d_w32, allows remote attackers to cause a denial of service (application crash) via a packet fragment with a large total data size, which triggers an application abort when memory allocation fails.
Exploit prediction
2.36% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- secunia.com http://secunia.com/advisories/19208 referenced PoC, tagged "exploit" by a source, unverified
- aluigi.altervista.org http://aluigi.altervista.org/adv/enetx-adv.txt referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
References
-
secunia.com
/advisories/19208
third-party-advisory, exploit, vendor-advisory
-
aluigi.altervista.org
/adv/enetx-adv.txt
exploit
-
lists.grok.org.uk
/pipermail/full-disclosure/2006-March/043541.html
mailing-list
-
securityfocus.com
/archive/1/427465/100/0/threaded
mailing-list
-
securitytracker.com
/id?1015767
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/25158
vdb-entry
-
securityfocus.com
/bid/17087
vdb-entry
-
vupen.com
/english/advisories/2006/0940
vdb-entry
-
osvdb.org
/23845
vdb-entry
Sources
- CVE List CVE-2006-1195
- NVD CVE-2006-1195
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.