CVE-2007-4375 json
The administrative interface (aka DkService.exe) in Diskeeper 9 Professional, 2007 Pro Premier, and probably other versions exposes a memor…
published 2007-08-16 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-4358
- cvss
- 5.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.4%
- EPSS 3.4% chance of exploitation in 30 days, percentile 88%
- public exploits
- 1
- Exploit-DB
Summary
The administrative interface (aka DkService.exe) in Diskeeper 9 Professional, 2007 Pro Premier, and probably other versions exposes a memory comparison function via RPC over TCP, which allows remote attackers to (1) obtain sensitive information (process memory contents), as demonstrated by an attack that obtains module base addresses to defeat Address Space Layout Randomization (ASLR); or (2) cause a denial of service (application crash) via an out-of-bounds address.
Timeline
- Published
- First public exploit (EDB-4292)
Exploit prediction
3.38% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-4292 Diskeeper 9 - Remote Memory Disclosure remote, 2007-08-17
- lists.grok.org.uk http://lists.grok.org.uk/pipermail/full-disclosure/2007-August/065245.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:P/I:N/A:P |
References
-
lists.grok.org.uk
/pipermail/full-disclosure/2007-August/065245.html
mailing-list, exploit
-
secunia.com
/advisories/26431
third-party-advisory, vendor-advisory
-
securityfocus.com
/bid/25320
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/36008
vdb-entry
-
osvdb.org
/39546
vdb-entry
-
osvdb.org
/39547
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/36007
vdb-entry
-
securityfocus.com
/archive/1/476954/100/0/threaded
mailing-list
-
securityreason.com
/securityalert/3018
third-party-advisory
Sources
- CVE List CVE-2007-4375
- NVD CVE-2007-4375
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.