CVE-2022-34746 json
An insufficient entropy vulnerability caused by the improper use of randomness sources with low entropy for RSA key pair generation was fou…
published 4y ago modified 4mo ago also EUVD-2022-37695
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 32%
- public exploits
- 0
- none known
Summary
An insufficient entropy vulnerability caused by the improper use of randomness sources with low entropy for RSA key pair generation was found in Zyxel GS1900 series firmware versions prior to V2.70. This vulnerability could allow an unauthenticated attacker to retrieve a private key by factoring the RSA modulus N in the certificate of the web administration interface.
Patch / fix
- zyxel gs1900-8_firmware 2.70\(aahh.3\)c0
- zyxel gs1900-8hp_firmware 2.70\(aahi.3\)c0
- zyxel gs1900-10hp_firmware 2.70\(aazi.3\)c0
- zyxel gs1900-16_firmware 2.70\(aahj.3\)c0
- zyxel gs1900-24_firmware 2.70\(aahl.3\)c0
- zyxel gs1900-24e_firmware 2.70\(aahk.3\)c0
- zyxel gs1900-24ep_firmware 2.70\(abto.3\)c0
- zyxel gs1900-24hpv2_firmware 2.70\(abtp.3\)c0
- zyxel gs1900-48_firmware 2.70\(aahn.3\)c0
- zyxel gs1900-48hpv2_firmware 2.70\(abtq.3\)c0
Is CVE-2022-34746 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.38% chance of exploitation in the next 30 days, higher than 32% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- Zyxel Zyxel GS1900 series firmware
Classification
- Weakness
-
- CWE-331 Insufficient Entropy
References
Sources
- CVE List CVE-2022-34746
- NVD CVE-2022-34746
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.