CVE-2012-0789

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

A fix is available — apply it.

Memory leak in the timezone functionality in PHP before 5.3.9 allows remote attackers to cause a denial of service (memory consumption) by triggering many strtotime function calls, which are not properly handled by the php_date_parse_tzfile cache.

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

Published

February 14, 2012

Last Modified

April 29, 2026

Vendor Advisories for CVE-2012-0789(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatphp-0:5.1.6-39.el5_82012-06-27redhat
redhatphp53-0:5.3.3-13.el5_82012-06-27redhat
redhatphp-0:5.3.3-14.el6_32012-06-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Frequently asked(4)

What is CVE-2012-0789?
CVE-2012-0789 is a none vulnerability published on February 14, 2012. Memory leak in the timezone functionality in PHP before 5.3.9 allows remote attackers to cause a denial of service (memory consumption) by triggering many strtotime function calls, which are not properly handled by the phpdateparse_tzfile cache.
When was CVE-2012-0789 disclosed?
CVE-2012-0789 was first published in the National Vulnerability Database on February 14, 2012, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2012-0789 actively exploited?
CVE-2012-0789 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 94.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2012-0789?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2012-0789, 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-2012-0789

Explore →

Is Your Infrastructure Affected by CVE-2012-0789?

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