Improper random reading in CIRCL
Medium5.3CVE-2023-1732 · Published May 10, 2023
### Impact When sampling randomness for a shared secret, the implementation of Kyber and FrodoKEM, did not check whether `crypto/rand.Read()` returns an error. In rare deployment cases (error thrown by the `Read()` function), this could lead to a predictable shared secret. The tkn20 and blindrsa components did not check whether enough randomness was returned from the user provided randomness source. Typically the user provides `crypto/rand.Reader`, which in the vast majority of cases will always return the right number random bytes. In the cases where it does not, or the user provides a source that does not, the blinding for blindrsa is weak and integrity of the plaintext is not ensured in tkn20. ### Patches The fix was introduced in CIRCL v. 1.3.3
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| CIRCL Go | < 1.3.3 | 1.3.3 |
Details and references
More Cloudflare advisories
All Cloudflare| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Dec 122023 | Unbounded queuing of path validation messages in cloudflare-quiche | Medium5.3 | 0.19.1 |
| Dec 52023 | Resource exhaustion via memory leak in tokio-boring | Medium5.3 | 4.1.0 |
| Nov 212023 | WebSocket message can cause crash | Medium | v1.20231121.0 |
| Aug 32023 | Directory traversal vulnerability in Cloudflare Wrangler | Medium5.7 | 3.1.1+1 more |
| May 122023 | Buffer under-read in workerd | Medium6.5 | v1.20230419.0 |
| Mar 212023 | Local Privilege Escalation Vulnerability in cloudflared's Installer | High7.5 | 2023.3.1 |