CVE-2022-4304

Timing Oracle in RSA Decryption

MEDIUM
5.9
CVSS Score
Published: February 8, 2023 at 07:04 PM UTC
Updated: October 14, 2026 at 03:16 PM UTC
4 products affected across 2 vendorsOpenSSLNetwork SecurityEndpoint Security

Using OpenSSL by OpenSSL?

Get instant alerts when new vulnerabilities affect OpenSSL - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.9
Exploit prediction
EPSS 24%
SSVC
No known exploit

Description

A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichenbacher style attack. To achieve a successful decryption an attacker would have to be able to send a very large number of trial messages for decryption. The vulnerability affects all RSA padding modes: PKCS#1 v1.5, RSA-OEAP and RSASVE. For example, in a TLS connection, RSA is commonly used by a client to send an encrypted pre-master secret to the server. An attacker that had observed a genuine connection between a client and a server could use this flaw to send trial messages to the server and record the time taken to process them. After a sufficiently large number of messages the attacker could recover the pre-master secret used for the original connection and thus be able to decrypt the application data sent over that connection.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versions1.0.2 ≤ v < 1.0.2zg1.1.1 ≤ v < 1.1.1t3.0.0 ≤ v < 3.0.81.0.21.1.13.0.0
Affected range stops below 1.0.2zg, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.1.1t, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.0.8, so it looks safe — our inference, not a vendor statement
All versionsv < 7.2.40
Affected range stops below 7.2.40, so it looks safe — our inference, not a vendor statement
2.7.0 ≤ v < 2.7.112.8.0 ≤ v < 3.7.343.8.0 ≤ v < 3.11.224.0.0 ≤ v < 4.3.164.4.0 ≤ v < 4.6.3
Affected range stops below 2.7.11, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.11.22, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.7.34, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.3.16, so it looks safe — our inference, not a vendor statement
Affected range stops below 4.6.3, so it looks safe — our inference, not a vendor statement
All versionsv < 3.2.1
Affected range stops below 3.2.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.9MEDIUMCISA-ADP
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-203

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card