CVE-2022-29035 json
In JetBrains Ktor Native before version 2.0.0 random values used for nonce generation weren't using SecureRandom implementations
published 4y ago modified 4mo ago also EUVD-2022-33465
- cvss
- 3.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
In JetBrains Ktor Native before version 2.0.0 random values used for nonce generation weren't using SecureRandom implementations
Patch / fix
- jetbrains ktor 2.0.0
- github.com/ktorio/ktor#2776 pull request
- jetbrains.com/privacy-security/issues-fixed/ advisory
Is CVE-2022-29035 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 FencerExploit prediction
0.62% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 3.3 | CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N |
| NVD | 3.1 | 2.7 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 4.0 | AV:N/AC:L/Au:S/C:P/I:N/A:N |
Affected products
- JetBrains Ktor
Classification
- Weakness
-
- CWE-330 Use of Insufficiently Random Values
References
-
github.com
/ktorio/ktor/pull/2776
patch, third-party-advisory
-
jetbrains.com
/privacy-security/issues-fixed/
patch, third-party-advisory
Sources
- CVE List CVE-2022-29035
- NVD CVE-2022-29035
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.