RSA implementation bug in AVX512IFMA instructions
Noroxi assessment
Priority: Plan (action score 53/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 45.6% (FIRST EPSS); higher than 98.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: openssl (Alpine:v3.17) 0; openssl-src (crates.io) 300.0.9; openssl (Debian:12) 3.0.4-2.
Add it to your regular patch cycle. Upgrade to openssl (Alpine:v3.17) 0; openssl-src (crates.io) 300.0.9; openssl (Debian:12) 3.0.4-2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
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.
- Published
- Jul 1, 2022
- Updated
- Jun 17, 2026
- EPSS
- 45.7% · 99th percentile
- CWE
- CWE-787
Report tools
Action score
53
Plan
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 14 / 30 · 45.7%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| openssl | openssl | cpe:2.3:a:openssl:openssl |
| netapp | h410s | cpe:2.3:h:netapp:h410s |
| netapp | snapcenter | cpe:2.3:a:netapp:snapcenter |
| netapp | h410c firmware | cpe:2.3:o:netapp:h410c_firmware |
| netapp | h410c | cpe:2.3:h:netapp:h410c |
| netapp | h300s firmware | cpe:2.3:o:netapp:h300s_firmware |
| netapp | h300s | cpe:2.3:h:netapp:h300s |
| netapp | h500s firmware | cpe:2.3:o:netapp:h500s_firmware |
| netapp | h500s | cpe:2.3:h:netapp:h500s |
| netapp | h700s firmware | cpe:2.3:o:netapp:h700s_firmware |
| netapp | h700s | cpe:2.3:h:netapp:h700s |
| netapp | h410s firmware | cpe:2.3:o:netapp:h410s_firmware |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- netapp h300s firmwareall versions
- netapp h410c firmwareall versions
- netapp h410s firmwareall versions
- netapp h500s firmwareall versions
- netapp h700s firmwareall versions
- netapp snapcenterall versions
- openssl openssl3.0.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (openssl). Independent of NVD's CPE analysis and usually ahead of it.
OpenSSL OpenSSL
- Affects OpenSSL 3.0.4affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.17 | openssl | before 0 | 0 |
| crates.io | openssl-src | from 300.0.8 · before 300.0.9 | 300.0.9 |
| Debian:12 | openssl | before 3.0.4-2 | 3.0.4-2 |
| openSUSE:Tumbleweed | openssh | before 9.3p1-1.1 | 9.3p1-1.1 |
| openSUSE:Tumbleweed | openssl-3 | before 3.0.5-1.1 | 3.0.5-1.1 |
Same product
openssl: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-0160The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packets, which allows remKEV90Now
- CVE-2021-3711SM2 Decryption Buffer Overflow65This week
- CVE-2003-0545Double free vulnerability in OpenSSL 0.9.7 allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code 65This week
- CVE-2016-2108The ASN.1 implementation in OpenSSL before 1.0.1o and 1.0.2 before 1.0.2c allows remote attackers to execute arbitrary code or cause a denia62This week
- CVE-2016-6309statem/statem.c in OpenSSL 1.1.0a does not consider memory-block movement after a realloc call, which allows remote attackers to cause a den60This week
- CVE-2022-3786X.509 Email Address Variable Length Buffer Overflow58Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:openssl | 0 · Alpine:v3.17 | Package registry (OSV) |
| crates.io:openssl-src | 300.0.9 | Package registry (OSV) |
| debian:openssl | 3.0.4-2 · Debian:12 | Package registry (OSV) |
| opensuse:openssh | 9.3p1-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| opensuse:openssl-3 | 3.0.5-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×3
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:16 | 2022-09-24 |
| Proof-of-concept repository on GitHub | stars:1 | 2022-11-11 |
| Proof-of-concept repository on GitHub | stars:1 | 2023-02-21 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+85 d
- TodayOct 12, 2026+1565 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.