CVE-2006-3824 json
systeminfo.c for Sun Solaris allows local users to read kernel memory via a 0 variable count argument to the sysinfo system call, which cau…
published 2006-07-25 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-3818
- cvss
- 4.9
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 2
- Exploit-DB
Summary
systeminfo.c for Sun Solaris allows local users to read kernel memory via a 0 variable count argument to the sysinfo system call, which causes a -1 argument to be used by the copyout function. NOTE: this issue has been referred to as an integer overflow, but it is probably more like a signedness error or integer underflow.
Patch / fix
Timeline
- First public exploit (EDB-2067)
- Published
Exploit prediction
0.99% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-2241 Solaris 10 sysinfo(2) - Local Kernel Memory Disclosure (2) local, 2006-08-22
- EDB-2067 Solaris 10 - 'sysinfo()' Local Kernel Memory Disclosure (1) local, 2006-07-24
- securityfocus.com http://www.securityfocus.com/bid/19104 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.9 | AV:L/AC:L/Au:N/C:C/I:N/A:N |
References
-
securityfocus.com
/bid/19104
vdb-entry, exploit, patch
-
sunsolve.sun.com
/search/document.do?assetkey=1-26-102343-1
vendor-advisory
-
securitytracker.com
/id?1016555
vdb-entry
-
securityfocus.com
/archive/1/440849/100/100/threaded
mailing-list
-
vupen.com
/english/advisories/2006/2936
vdb-entry
-
secunia.com
/advisories/21148
third-party-advisory
-
idefense.com
/intelligence/vulnerabilities/display.php?id=410
third-party-advisory
-
securityfocus.com
/archive/1/440986/100/100/threaded
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/27901
vdb-entry
Sources
- CVE List CVE-2006-3824
- NVD CVE-2006-3824
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.