Description
The memory_limit functionality in PHP 4.x up to 4.3.7, and 5.x up to 5.0.0RC3, under certain conditions such as when register_globals is enabled, allows remote attackers to execute arbitrary code by triggering a memory_limit abort during execution of the zend_hash_init function and overwriting a HashTable destructor pointer before the initialization of key data structures is complete.
Product(s):
- OpenPKG 2.0
- OpenPKG 2.1
- PHP
- PHP PHP 4.0.0
- PHP PHP 4.0.1
- PHP 4.0.1 -
- PHP 4.0.1 Patch 1
- PHP 4.0.1 Patch 2
- PHP 4.0.1 Release Candidate 2
- PHP 4.0.1 Release Candidate
- PHP PHP 4.0.2
- PHP 4.0.2 Release Candidate 1
- PHP PHP 4.0.3
- PHP 4.0.3 Patch 1
- PHP 4.0.3 Release Candidate 1
- PHP 4.0.3 Release Candidate 2
- PHP PHP 4.0.4
- PHP 4.0.4 -
- PHP 4.0.4 Release Candidate 1
- PHP 4.0.4 Release Candidate 2
- PHP 4.0.4 Release Candidate 3
- PHP 4.0.4 Release Candidate 4
- PHP 4.0.4 Release Candidate 5
- PHP 4.0.4 Release Candidate 6
- PHP PHP 4.0.5
- PHP 4.0.5 -
- PHP 4.0.5 Release Candidate 1
- PHP 4.0.5 Release Candidate 2
- PHP 4.0.5 Release Candidate 3
- PHP 4.0.5 Release Candidate 4
- PHP 4.0.5 Release Candidate 5
- PHP 4.0.5 Release Candidate 6
- PHP 4.0.5 Release Candidate 7
- PHP 4.0.5 Release Candidate 8
- PHP PHP 4.0.6
- PHP 4.0.6 -
- PHP 4.0.6 Release Candidate 1
- PHP 4.0.6 Release Candidate 2
- PHP 4.0.6 Release Candidate 3
- PHP 4.0.6 Release Candidate 4
- PHP PHP 4.0.7
- PHP 4.0.7 -
- PHP 4.0.7 Release Candidate 1
- PHP 4.0.7 Release Candidate 2
- PHP 4.0.7 Release Candidate 3
- PHP 4.0.0
- PHP 4.0 -
- PHP PHP 4.0 Beta 1
- PHP PHP 4.0 Beta 2
- PHP PHP 4.0 Beta 3
- PHP PHP 4.0 Beta 4
- PHP PHP 4.0 Beta 4 Patch Level 1
- PHP 4.0 Release Candidate 1
- PHP 4.0 Release Candidate 2
- PHP PHP 4.1.0
- PHP 4.1.0 -
- PHP 4.1.0 Release Candidate 1
- PHP 4.1.0 Release Candidate 2
- PHP 4.1.0 Release Candidate 3
- PHP 4.1.0 Release Candidate 4
- PHP 4.1.0 Release Candidate 5
- PHP PHP 4.1.1
- PHP PHP 4.1.2
- PHP 4.1.0
- PHP PHP 4.2.0
- PHP 4.2.0 -
- PHP 4.2.0 Release Candidate 1
- PHP 4.2.0 Release Candidate 2
- PHP 4.2.0 Release Candidate 3
- PHP 4.2.0 Release Candidate 4
- PHP PHP 4.2.1
- PHP 4.2.1 -
- PHP 4.2.1 Release Candidate 1
- PHP 4.2.1 Release Candidate 2
- PHP PHP 4.2.2
- PHP PHP 4.2.3
- PHP 4.2.3 -
- PHP 4.2.3 Release Candidate 1
- PHP 4.2.3 Release Candidate 2
- PHP 4.2.0
- PHP PHP 4.3.0
- PHP 4.3.0 -
- PHP 4.3.0 Alpha1
- PHP 4.3.0 Alpha2
- PHP 4.3.0 Alpha3
- PHP 4.3.0 Dev
- PHP 4.3.0 Patch re1
- PHP 4.3.0 Patch re2
- PHP 4.3.0 Release Candidate 1
- PHP 4.3.0 Release Candidate 2
- PHP 4.3.0 Release Candidate 3
- PHP 4.3.0 Release Candidate 4
- PHP PHP 4.3.1
- PHP PHP 4.3.2
- PHP 4.3.2 -
- PHP 4.3.2 Release Candidate 1
- PHP 4.3.2 Release Candidate 2
- PHP 4.3.2 Release Candidate 3
- PHP 4.3.2 Release Candidate 4
- +38 additional
Question to Ask Vendors:
- Can you confirm whether your systems are affected by CVE-2004-0594, and if so, what steps are you currently taking to mitigate this vulnerability?
- What is your estimated timeline for fully resolving CVE-2004-0594 in your products or services, and how will you communicate updates on this issue to us as your customer?
Recommended Actions:
- Check out the advisory links provided below.