CVE-2003-0166

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 14%CVSS: —Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
—
EG Score
0.0(none)
EPSS
96.1%
KEV
Not listed

Published

April 2, 2003

Last Modified

June 16, 2026

References (12)

Data Freshness Timeline

(refreshed 3× in last 7d / 21× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:22 UTCEPSS rescore
  2. 2026-07-11 08:22 UTCEPSS rescore
  3. 2026-07-08 15:09 UTCEPSS rescore
  4. 2026-07-06 02:19 UTCEPSS rescore
  5. 2026-07-04 06:26 UTCEPSS rescore
  6. 2026-07-02 14:00 UTCEPSS rescore
  7. 2026-06-28 04:52 UTCEPSS rescore
  8. 2026-06-27 03:04 UTCEPSS rescore
  9. 2026-06-23 21:29 UTCEPSS rescore
  10. 2026-06-22 14:22 UTCEPSS rescore
  11. 2026-06-19 19:22 UTCEPSS rescore
  12. 2026-06-19 19:22 UTCEPSS rescore
  13. 2026-06-18 17:49 UTCEPSS rescore
  14. 2026-06-18 17:49 UTCEPSS rescore
  15. 2026-06-17 17:49 UTCEPSS rescore
  16. 2026-06-17 17:49 UTCEPSS rescore
  17. 2026-06-16 17:49 UTCEPSS rescore
  18. 2026-06-16 17:49 UTCEPSS rescore
  19. 2026-06-15 17:43 UTCEPSS rescore
  20. 2026-06-14 23:13 UTCEPSS rescore
  21. 2026-06-14 23:13 UTCEPSS rescore
  22. 2026-06-13 22:56 UTCEPSS rescore
  23. 2026-06-12 23:08 UTCEPSS rescore
  24. 2026-06-11 13:55 UTCEPSS rescore
  25. 2026-06-10 22:13 UTCEPSS rescore
Show 29 more
  1. 2026-06-10 13:17 UTCEPSS rescore
  2. 2026-06-07 15:21 UTCEPSS rescore
  3. 2026-06-06 13:44 UTCEPSS rescore
  4. 2026-06-06 13:44 UTCEPSS rescore
  5. 2026-06-06 13:44 UTCEPSS rescore
  6. 2026-06-05 22:43 UTCEPSS rescore
  7. 2026-06-05 22:43 UTCEPSS rescore
  8. 2026-06-04 13:09 UTCEPSS rescore
  9. 2026-06-02 20:10 UTCEPSS rescore
  10. 2026-06-01 13:49 UTCEPSS rescore
  11. 2026-06-01 13:49 UTCEPSS rescore
  12. 2026-05-31 22:28 UTCEPSS rescore
  13. 2026-05-31 17:45 UTCEG score recompute
  14. 2026-05-31 17:45 UTCGHSA enrichment
  15. 2026-05-29 13:40 UTCEPSS rescore
  16. 2026-05-29 13:40 UTCEPSS rescore
  17. 2026-05-28 13:42 UTCEPSS rescore
  18. 2026-05-28 13:42 UTCEPSS rescore
  19. 2026-05-28 13:42 UTCEPSS rescore
  20. 2026-05-27 13:37 UTCEPSS rescore
  21. 2026-05-26 13:41 UTCEPSS rescore
  22. 2026-05-26 13:41 UTCEPSS rescore
  23. 2026-05-24 16:42 UTCEPSS rescore
  24. 2026-05-22 21:15 UTCEPSS rescore
  25. 2026-05-20 22:36 UTCEPSS rescore
  26. 2026-05-20 11:20 UTCEPSS rescore
  27. 2026-05-20 11:20 UTCEPSS rescore
  28. 2026-05-18 21:29 UTCEPSS rescore
  29. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(3 references)

Working exploit code is in the public domain (3 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-22425✓ verified
    First seen Mar 26, 2003

    PHP 4.x - 'socket_recv()' Signed Integer Memory Corruption

    Open source ↗
  • Exploit-DBEDB-22426✓ verified
    First seen Mar 26, 2003

    PHP 4.x - 'socket_recvfrom()' Signed Integer Memory Corruption

    Open source ↗
  • Exploit-DBEDB-22419✓ verified
    First seen Mar 25, 2003

    PHP 4.3 - 'socket_iovec_alloc()' Integer Overflow

    Open source ↗

Frequently asked(4)

What is CVE-2003-0166?
CVE-2003-0166 is a none vulnerability published on April 2, 2003. 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) socketrecv, (2) socketrecvfrom, and possibly other functions.
When was CVE-2003-0166 disclosed?
CVE-2003-0166 was first published in the National Vulnerability Database on April 2, 2003, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2003-0166 actively exploited?
CVE-2003-0166 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2003-0166?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2003-0166, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2003-0166

Explore →

Is Your Infrastructure Affected by CVE-2003-0166?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs