CVE-2006-1593 json
The (1) ZD_MissingPlayer, (2) ZD_UseItem, and (3) ZD_LoadNewClientLevel functions in sv_main.cpp for (a) Zdaemon 1.08.01 and (b) X-Doom all…
published 2006-04-03 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-1594
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.7%
- EPSS 4.7% chance of exploitation in 30 days, percentile 91%
- public exploits
- 1
- Exploit-DB
Summary
The (1) ZD_MissingPlayer, (2) ZD_UseItem, and (3) ZD_LoadNewClientLevel functions in sv_main.cpp for (a) Zdaemon 1.08.01 and (b) X-Doom allows remote attackers to cause a denial of service (crash) via an invalid player slot or item number, which causes an invalid memory access, possibly due to an invalid array index.
Timeline
- First public exploit (EDB-27547)
- Published
Exploit prediction
4.69% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-27547 Zdaemon 1.8.1 - Multiple Vulnerabilities dos, 2006-03-31
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-399 Resource Management Errors
References
-
vupen.com
/english/advisories/2006/1198
vdb-entry, vendor-advisory
-
vupen.com
/english/advisories/2006/1199
vdb-entry, vendor-advisory
-
secunia.com
/advisories/19509
third-party-advisory, vendor-advisory
-
secunia.com
/advisories/19496
third-party-advisory, vendor-advisory
-
securityfocus.com
/archive/1/429521/100/0/threaded
mailing-list
-
securityfocus.com
/bid/17340
vdb-entry
-
securityreason.com
/securityalert/662
third-party-advisory
- aluigi.altervista.org /adv/zdaebof-adv.txt
-
lists.grok.org.uk
/pipermail/full-disclosure/2006-March/044775.html
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/25593
vdb-entry
Sources
- CVE List CVE-2006-1593
- NVD CVE-2006-1593
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.