CVE-2003-0166 in the critical feed json
Integer signedness error in emalloc() function for PHP before 4.3.2 allow remote attackers to cause a denial of service (memory consumption…
published 2003-03-27 23 y ago modified 2026-06-16 4 mo ago also EUVD-2003-0162
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 14.1%
- EPSS 14.1% chance of exploitation in 30 days, percentile 96%
- public exploits
- 3
- Exploit-DB
Summary
Integer signedness error in emalloc() function for PHP before 4.3.2 allow remote attackers to cause a denial of service (memory consumption) and possibly execute arbitrary code via negative arguments to functions such as (1) socket_recv, (2) socket_recvfrom, and possibly other functions.
Timeline
- First public exploit (EDB-22419)
- Published
Exploit prediction
14.12% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-22426 PHP 4.x - 'socket_recvfrom()' Signed Integer Memory Corruption dos, 2003-03-26
- EDB-22425 PHP 4.x - 'socket_recv()' Signed Integer Memory Corruption dos, 2003-03-26
- EDB-22419 PHP 4.3 - 'socket_iovec_alloc()' Integer Overflow dos, 2003-03-25
- securityfocus.com http://www.securityfocus.com/bid/7198 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/7197 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Technology feeds
References
-
securityfocus.com
/bid/7198
vdb-entry, exploit, vendor-advisory
-
securityfocus.com
/bid/7197
vdb-entry, exploit, vendor-advisory
-
distro.conectiva.com.br
/atualizacoes/?id=a&anuncio=000691
vendor-advisory
-
marc.info
/?l=bugtraq&m=104931415307111&w=2
mailing-list
-
marc.info
/?l=bugtraq&m=104878100719467&w=2
mailing-list
-
marc.info
/?l=bugtraq&m=104869828526885&w=2
mailing-list
Sources
- CVE List CVE-2003-0166
- NVD CVE-2003-0166
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.