CVE-2022-29242 json
Buffer Overflow on creating key transport blob in GOST Engine
published 2022-05-24 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-33599
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
GOST engine is a reference implementation of the Russian GOST crypto algorithms for OpenSSL. TLS clients using GOST engine when ciphersuite `TLS_GOSTR341112_256_WITH_KUZNYECHIK_CTR_OMAC` is agreed and the server uses 512 bit GOST secret keys are vulnerable to buffer overflow. GOST engine version 3.0.1 contains a patch for this issue. Disabling ciphersuite `TLS_GOSTR341112_256_WITH_KUZNYECHIK_CTR_OMAC` is a possible workaround.
Patch / fix
- gost_engine_project gost_engine 3.0.1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
1.71% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).
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:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Affected products
- gost-engine engine
Classification
- Weakness
-
- CWE-120 Buffer Copy without Checking Size of Input
References
-
github.com
/gost-engine/engine/commit/7df766124f87768b43b9e8947c5a01e17545772c
patch, third-party-advisory
-
github.com
/gost-engine/engine/commit/b2b4d629f100eaee9f5942a106b1ccefe85b8808
patch, third-party-advisory
-
github.com
/gost-engine/engine/commit/c6655a0b620a3e31f085cc906f8073fe81b2fad3
patch, third-party-advisory
-
github.com
/gost-engine/engine/security/advisories/GHSA-2rmw-8wpg-vgw5
third-party-advisory
-
github.com
/gost-engine/engine/releases/tag/v3.0.1
release-notes, third-party-advisory
Sources
- CVE List CVE-2022-29242
- NVD CVE-2022-29242
Fencer Vulns 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.