CVE-2022-2274 — openssl-src
CRITICALCVE-2022-2274 is a critical-severity (CVSS 9.8) Out-of-bounds Write vulnerability in openssl-src. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for openssl-src — see the affected versions and patch details below.
RSA implementation bug in AVX512IFMA instructions
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
openssl-srcReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
The OpenSSL 3.0.4 release introduced a serious bug in the RSA implementation for X86_64 CPUs supporting the AVX512IFMA instructions. This issue makes the RSA implementation with 2048 bit private keys incorrect on such machines and memory corruption will happen during the computation. As a consequence of the memory corruption an attacker may be able to trigger a remote code execution on the machine performing the computation. SSL/TLS servers or other servers using 2048 bit RSA private keys running on machines supporting AVX512IFMA instructions of the X86_64 architecture are affected by this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | openssl-src | ≥ 300.0.8&&< 300.0.9 | 300.0.9cargo update -p openssl-src --precise 300.0.9 |
Affected Products
h300s firmwarenetapph410c firmwarenetapph410s firmwarenetapph500s firmwarenetapph700s firmwarenetappsnapcenternetappResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openssl-src, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openssl-src to 300.0.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-2274 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This vulnerability was introduced in OpenSSL 3.0.4 via upstream commit 10d8a10. The versions of OpenSSL as shipped with Red Hat Enterprise Linux are not affected by this flaw, as they did not backport the upstream commit that introduced this issue.
Disabling the AVX512IFMA instruction set extension can effectively mitigate this flaw: ``` export OPENSSL_ia32cap=:~0x200000 ```Source: Red Hat security advisory for CVE-2022-2274 (CC BY 4.0)
Frequently Asked Questions
Is CVE-2022-2274 in your dependencies?
Find it across crates.io, including transitive dependencies.