Skip to main content
Mallory
MediumVulnerability

CVE-2022-4304: RSA Decryption Timing Side Channel in OpenSSL

Published Feb 8, 2023 · Updated 12 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS5.9Medium · v3.1
EPSS23.5%98th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendors
StormshieldOpenSSL Software Foundation
IdentifiersCVE-2022-4304CWE-385

CVE-2022-4304 is a timing side-channel vulnerability in OpenSSL's RSA decryption implementation. An attacker can submit a very large number of trial ciphertexts and measure decryption processing times to potentially recover plaintext through a network-based Bleichenbacher-style attack. The flaw affects PKCS#1 v1.5, RSA-OAEP, and RSASVE padding modes. In TLS connections using RSA key exchange, exploitation can reveal the pre-master secret and permit decryption of captured application data.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises the confidentiality of RSA-encrypted plaintext. For an observed TLS connection using RSA key exchange, recovery of the pre-master secret enables decryption of application data from that connection. Exploitation has high attack complexity but requires neither privileges nor user interaction. No direct integrity or availability impact is established for this vulnerability.

Mitigation

If you can’t patch tonight, do this now.

No complete workaround is established. Until patched, restrict attacker access to services performing vulnerable RSA private-key decryptions and minimize use of affected RSA decryption paths where possible. These exposure-reduction measures do not replace installing the fix.

Remediation

Patch, then assume compromise.

Upgrade to OpenSSL 3.0.8, 1.1.1t, or 1.0.2zg, as applicable, or install a vendor-supported package containing the backported fix. OpenSSL 1.0.2zg is available through paid support. Update products that bundle affected OpenSSL implementations using their vendor-provided security releases. For openssl-src, fixed versions are 111.25.0 for the 1.1.1 line and 300.0.12 for the 3.0.x line. Restart all services linked to the updated OpenSSL library, or reboot affected systems, so the corrected code is loaded.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
OpenSSL Software FoundationOpensslapplication
StormshieldEndpoint Securityapplication
StormshieldSslvpnapplication
StormshieldStormshield Network Securityapplication
FAQ

Frequently asked questions

Is CVE-2022-4304 exploited in the wild?
As of Nov 6, 2026, Mallory has no reports of CVE-2022-4304 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2022-4304?
As of Nov 6, 2026, Mallory has found no public exploit for CVE-2022-4304.
Is there a patch for CVE-2022-4304?
Upgrade to OpenSSL 3.0.8, 1.1.1t, or 1.0.2zg, as applicable, or install a vendor-supported package containing the backported fix. OpenSSL 1.0.2zg is available through paid support.
What products are affected by CVE-2022-4304?
OpenSSL Software Foundation Openssl, Stormshield Endpoint Security, Stormshield Sslvpn, and Stormshield Network Security.
How severe is CVE-2022-4304?
CVE-2022-4304 has a CVSS v3.1 score of 5.9 (Medium) and an EPSS score of 23.5% (98th percentile) as of Nov 6, 2026.
Activity feed

Recent activity

53 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+32 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.