CVE-2006-4392 json
The Mach kernel, as used in operating systems including (1) Mac OS X 10.4 through 10.4.7 and (2) OpenStep before 4.2, allows local users to…
published 2006-10-02 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-4380
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 2
- Exploit-DB
Summary
The Mach kernel, as used in operating systems including (1) Mac OS X 10.4 through 10.4.7 and (2) OpenStep before 4.2, allows local users to gain privileges via a parent process that forces an exception in a setuid child and uses Mach exception ports to modify the child's thread context and task address space in a way that causes the child to call a parent-controlled function.
Patch / fix
Timeline
- First public exploit (EDB-2464)
- Published
Exploit prediction
1.58% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
References
-
lists.apple.com
/archives/security-announce/2006/Sep/msg00002.html
vendor-advisory, patch
-
securityfocus.com
/bid/20271
vdb-entry, patch
-
secunia.com
/advisories/22187
third-party-advisory, patch, vendor-advisory
-
matasano.com
/log/530/matasano-advisory-macos-x-mach-exception-server-privilege-escalation/
vendor-advisory
-
securitytracker.com
/id?1016954
vdb-entry
-
vupen.com
/english/advisories/2006/3852
vdb-entry
-
securityfocus.com
/archive/1/447396/100/0/threaded
mailing-list
-
kb.cert.org
/vuls/id/838404
third-party-advisory, us-government-resource
-
osvdb.org
/29269
vdb-entry
-
us-cert.gov
/cas/techalerts/TA06-275A.html
third-party-advisory, us-government-resource
-
securityreason.com
/securityalert/1663
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/29281
vdb-entry
Sources
- CVE List CVE-2006-4392
- NVD CVE-2006-4392
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.