CVE-2008-0927 json
dhost.exe in Novell eDirectory 8.7.3 before sp10 and 8.8.2 allows remote attackers to cause a denial of service (CPU consumption) via an HT…
published 2008-04-14 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-0934
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 70.0%
- EPSS 70.0% chance of exploitation in 30 days, percentile 99.3%
- public exploits
- 1
- Exploit-DB
Summary
dhost.exe in Novell eDirectory 8.7.3 before sp10 and 8.8.2 allows remote attackers to cause a denial of service (CPU consumption) via an HTTP request with (1) multiple Connection headers or (2) a Connection header with multiple comma-separated values. NOTE: this might be similar to CVE-2008-1777.
Timeline
- Published
- First public exploit (EDB-5547)
Exploit prediction
70.05% chance of exploitation in the next 30 days, higher than 99.3% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-5547 Novell eDirectory < 8.7.3 SP 10 / 8.8.2 - HTTP headers Denial of Service dos, 2008-05-05
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
-
exploit-db.com
/exploits/5547
exploit, third-party-advisory, vdb-entry
-
novell.com
/support/viewContent.do?externalId=3829452&sliceId=1
vendor-advisory
-
securityfocus.com
/archive/1/491622/100/0/threaded
mailing-list, third-party-advisory, vdb-entry
-
securitytracker.com
/id?1019836
vdb-entry, third-party-advisory
-
secunia.com
/advisories/29805
third-party-advisory
-
vupen.com
/english/advisories/2008/1217/references
vdb-entry, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/41787
vdb-entry, third-party-advisory
-
securityfocus.com
/bid/28757
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2008-0927
- NVD CVE-2008-0927
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.