GHSA-xg9w-r469-m455: ZendFramework Potential Information Disclosure and Insufficient Entropy vulnerabilities
In Zend Framework 2, the Zend\Math\Rand component generates random bytes using the OpenSSL or Mcrypt extensions when available but will otherwise use PHP's mtrand() function as a fallback. All outputs from mtrand() are predictable for the same PHP process if an attacker can brute force the seed used by the Marsenne-Twister algorithm in a Seed Recovery Attack.
Published Jun 7, 2024
Affected packages
zendframework/zendframework
- Ecosystem
- Composer (PHP)
- Affected
- >= 2.0.0, < 2.0.8
- Fixed in
- 2.0.8
- Check
composer show zendframework/zendframework
zendframework/zendframework
- Ecosystem
- Composer (PHP)
- Affected
- >= 2.1.0, < 2.1.4
- Fixed in
- 2.1.4
- Check
composer show zendframework/zendframework
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
In Zend Framework 2, the Zend\Math\Rand component generates random bytes using the OpenSSL or Mcrypt extensions when available but will otherwise use PHP's mt_rand() function as a fallback. All outputs from mt_rand() are predictable for the same PHP process if an attacker can brute force the seed used by the Marsenne-Twister algorithm in a Seed Recovery Attack. This attack can be successfully applied with minimum effort if the attacker has access to either a random number from mt_rand() or a Session ID generated without using additional entropy. This makes mt_rand() unsuitable for generating non-trivial random bytes since it has Insufficient Entropy to protect against brute force attacks on the seed.
The Zend\Validate\Csrf component generates CSRF tokens by SHA1 hashing a salt, random number possibly generated using mt_rand() and a form name. Where the salt is known, an attacker can brute force the SHA1 hash with minimum effort to discover the random number when mt_rand() is utilised as a fallback to the OpenSSL and Mcrypt extensions. This constitutes an Information Disclosure where the recovered random number may itself be brute forced to recover the seed value and predict the output of other mt_rand() calls for the same PHP process. This may potentially lead to vulnerabilities in areas of an application where mt_rand() calls exist beyond the scope of Zend Framework.
References
- https://github.com/zendframework/zendframework/commit/6975695dfdb201bda0aea02bcc11b4a85ddc89fa
- https://github.com/zendframework/zendframework/commit/97b98e7208f93613ab358432e56b6e2245153807
- https://framework.zend.com/security/advisory/ZF2013-02
- https://github.com/FriendsOfPHP/security-advisories/blob/master/zendframework/zendframework/ZF2013-02.yaml
- https://github.com/advisories/GHSA-xg9w-r469-m455
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesGHSA-2fhr-8r8r-qp56
ZendFramework Information Disclosure and Insufficient Entropy vulnerability
medium5.3Jun 7, 2024GHSA-5gmf-3c43-q73v
ZendFramework vulnerable to Cross-site Scripting
medium6.1Jun 7, 2024GHSA-62f6-h68r-3jpw
Zendframework session validation vulnerability
medium6.5Jun 7, 2024GHSA-8q77-cv62-jj38
Zendframework has potential Cross-site Scripting vector in multiple view helpers
medium6.1Jun 7, 2024GHSA-fh7r-58q4-6387
Zendframework URL Rewrite vulnerability
medium4.7Jun 7, 2024GHSA-gff2-p6vm-3p8g
ZendFramework potential remote code execution in zend-mail via Sendmail adapter
medium6.5Jun 7, 2024
