dbcve.org
OpenSSLFramework / library

CVE-2022-4304

MEDIUM · 5.9 CVSS v3.1 Published 2023-02-08
Fix available
A fix is available. Upgrade to 1.0.2zg / 1.1.1t or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OpenSSL RSA decryption contains a timing-based side channel that allows an attacker to recover plaintext via Bleichenbacher-style attacks by sending many trial messages and measuring response times. The flaw affects all RSA padding modes (PKCS#1 v1.5, RSA-OEAP, RSASVE) and could expose pre-master secrets in TLS connections.

MitigationUpdate OpenSSL to the patched version. Consider migrating from RSA key exchange to ECDHE to eliminate RSA decryption attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenSSLFramework / library
Affected:>= 1.0.2, < 1.0.2zg>= 1.1.1, < 1.1.1t>= 3.0.0, < 3.0.8
Endpoint SecurityApplication
Affected:< 7.2.40
SslvpnApplication
Affected:< 3.2.1
Stormshield Network SecurityApplication
Affected:>= 2.7.0, < 2.7.11>= 2.8.0, < 3.7.34>= 3.8.0, < 3.11.22>= 4.0.0, < 4.3.16>= 4.4.0, < 4.6.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the OpenSSL version in use
    Run 'openssl version' on Linux/Unix systems, or check the OpenSSL DLL/library version on Windows systems. On Linux, you can also query the package manager (dpkg -l | grep openssl or rpm -qa | grep openssl)
    Affected if The installed version falls within any of these ranges: 1.0.2 through 1.0.2zf (any 1.0.2 version before 1.0.2zg), 1.1.1 through 1.1.1s (any 1.1.1 version before 1.1.1t), or 3.0.0 through 3.0.7 (any 3.0.x version before 3.0.8)
  2. Determine if RSA key exchange is enabled in TLS configurations
    Examine your server's TLS configuration files (such as httpd.conf, nginx.conf, or your TLS-terminating device settings). Look for cipher suites containing 'RSA' or 'RSA_EXPORT' in their names, such as TLS_RSA_WITH_AES_128_CBC_SHA or similar RSA-based cipher suites.
    Affected if RSA-based cipher suites are enabled and the server accepts RSA key exchange for TLS connections
  3. Check if clients can authenticate using RSA certificates
    Review TLS server settings to verify whether RSA-based client certificate authentication is permitted. This applies to scenarios where clients present RSA certificates for mutual TLS (mTLS) authentication.
    Affected if RSA client certificate authentication is enabled in your TLS server configuration
  4. Identify Stormshield product installations and versions
    For Stormshield Endpoint Security, check the installed version via the product's GUI or command-line tool. For Stormshield Sslvpn and Network Security appliances, check the firmware version through the admin interface or by running 'CLI version' or 'get system version' commands.
    Affected if Any Stormshield product is running a version below the fixed release: Endpoint Security < 7.2.40, Sslvpn < 3.2.1, or Network Security falls within any of these ranges: 2.7.0-2.7.10, 2.8.0-3.7.33, 3.8.0-3.11.21, 4.0.0-4.3.15, or 4.4.0-4.6.2

Your environment is affected if you are running a vulnerable OpenSSL version (1.0.2, 1.1.1, or 3.0.x before the fixed releases) OR a vulnerable Stormshield product version, AND you have RSA-based cipher suites or RSA client certificate authentication enabled in your TLS configurations.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.2zg / 1.1.1t / 2.7.11 or later
Fixed in 1.0.2zg1.1.1t2.7.11
Interim mitigation

Update OpenSSL to the patched version. Consider migrating from RSA key exchange to ECDHE to eliminate RSA decryption attack surface.

Recommended fix High confidence

OpenSSL: 3.0.8+ (or 1.1.1t+ / 1.0.2zg+); Endpoint Security: 7.2.40+; Sslvpn: 3.2.1+; Stormshield: 4.3.16+ (or latest available)

  1. Identify the specific product and version in use from the affected list (OpenSSL, Endpoint Security, Sslvpn, or Stormshield Network Security)
  2. For OpenSSL: Upgrade to version 1.0.2zg, 1.1.1t, or 3.0.8 (or later) depending on your current major version branch
  3. For SonicWall Endpoint Security: Upgrade to version 7.2.40 or later
  4. For SonicWall Sslvpn: Upgrade to version 3.2.1 or later
  5. For Stormshield Network Security: Upgrade to version 2.7.11, 3.7.34, 3.11.22, or 4.3.16 (or later) depending on your current branch
  6. After upgrade, verify the OpenSSL version using: openssl version -a
  7. Restart any services that use TLS to ensure the new library is loaded
Caveat Major OpenSSL version upgrades (e.g., 1.1.1 to 3.x) may introduce API/behavioral changes; test thoroughly before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in OpenSSL Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-4304 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-4304 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data