ZendFramework Information Disclosure and Insufficient Entropy vulnerability

published 2024-06-07 2y ago modified 2024-12-04 last yr.

cvss: 5.3; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

In Zend Framework, `Zend_Captcha_Word` (v1) and `Zend\Captcha\Word` (v2) generate a "word" for a CAPTCHA challenge by selecting a sequence of random letters from a character set. Prior to this advisory, the selection was performed using PHP's `internal array_rand()` function. This function does not generate sufficient entropy due to its usage of `rand()` instead of more cryptographically secure methods such as `openssl_pseudo_random_bytes()`. This could potentially lead to information disclosure should an attacker be able to brute force the random number generation.

Patch / fix

fixed in 1 links 1

packagist zendframework/zendframework 2.4.9

github.com/zendframework/zendframework@ced8ff9 commit

Is GHSA-2fhr-8r8r-qp56 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
packagist	zendframework/zendframework	>=2.0.0, <2.4.9	2.4.9

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-331 Insufficient Entropy

References

Sources

GitHub Advisory GHSA-2fhr-8r8r-qp56

Fencer Intel 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.