CVE-2004-0430 json
Stack-based buffer overflow in AppleFileServer for Mac OS X 10.3.3 and earlier allows remote attackers to execute arbitrary code via a Logi…
published 2004-05-06 22 y ago modified 2026-06-16 4 mo ago also EUVD-2004-0429
- cvss
- 5.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 41.3%
- EPSS 41.3% chance of exploitation in 30 days, percentile 98%
- public exploits
- 4
- Metasploit, Exploit-DB
Summary
Stack-based buffer overflow in AppleFileServer for Mac OS X 10.3.3 and earlier allows remote attackers to execute arbitrary code via a LoginExt packet for a Cleartext Password User Authentication Method (UAM) request with a PathName argument that includes an AFPName type string that is longer than the associated length field.
Patch / fix
Timeline
- First public exploit (EDB-9931)
- Published
Exploit prediction
41.30% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit exploit/osx/afp/loginext AppleFileServer LoginExt PathName Overflow metasploit exploit, average rank, 2004-05-03
- EDB-16863 AppleFileServer (OSX) - LoginExt PathName Overflow (Metasploit) remote, 2010-09-20
- EDB-9931 AppleFileServer 10.3.3 (OSX) - LoginEXT PathName Overflow (Metasploit) remote, 2004-03-03
- EDB-391 Apple Mac OSX 10.3.3 - AppleFileServer Overflow Remote Code Execution remote, 2004-08-13
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.1 | AV:N/AC:H/Au:N/C:P/I:P/A:P |
References
-
atstake.com
/research/advisories/2004/a050304-1.txt
vendor-advisory, patch
-
lists.apple.com
/mhonarc/security-announce/msg00049.html
vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/16049
vdb-entry
-
securitytracker.com
/id?1010039
vdb-entry
-
kb.cert.org
/vuls/id/648406
third-party-advisory, us-government-resource
- securiteam.com /securitynews/5QP0115CUO.html
-
secunia.com
/advisories/11539
third-party-advisory
Sources
- CVE List CVE-2004-0430
- NVD CVE-2004-0430
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.