Sign inStart freeBook a demo

What is CVE-2022-2068?A high-severity flaw in OpenSSL, explained.

High severity28 affected products
The short answer

CVE-2022-2068 is a high-severity flaw (CVSS 7.3) in OpenSSL, published on 21 June 2022. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 96%. If you run an affected version, plan in the vendor’s fix.

Check if it affects you →How to fix it

Published 21 June 2022. Record last updated 3 November 2025. We keep this page's data up to date.

What it does

What is CVE-2022-2068? In plain terms.

An attacker has to be already on the device with an ordinary user account, but a person has to take an action first. If it works, the attacker can read data, change data and take it offline.

The official description

In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise shell metacharacters to prevent command injection were found by code review. When the CVE-2022-1292 was fixed it was not discovered that there are other places in the script where the file names of certificates being hashed were possibly passed to a command executed through the shell. This script is distributed by some operating systems in a manner where it is automatically executed. On such operating systems, an attacker could execute arbitrary commands with the privileges of the script. Use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool. Fixed in OpenSSL 3.0.4 (Affected 3.0.0,3.0.1,3.0.2,3.0.3). Fixed in OpenSSL 1.1.1p (Affected 1.1.1-1.1.1o). Fixed in OpenSSL 1.0.2zf (Affected 1.0.2-1.0.2ze).

What kind of flaw is it?

  • CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
CVSS 3.1 scoreHigh · 7.3

How an attack on it works

Read straight from its severity rating, translated out of the shorthand.

  • Where an attacker can beAlready on the device
  • How hard it is to pull offEasy: no special conditions
  • Login needed firstAn ordinary user account
  • Does someone have to clickYes, a person has to take an action
  • What an attacker getsCan read data, change data and take it offline

Severity vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Exploitation

Is CVE-2022-2068 being exploited? Not that we know of.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 96%. That can change at any time, which is why we keep watching.

Known to be exploitedNoNot on the list of exploited flaws today
Chance of use in the next 30 days96%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Exploit likelihood fell
  3. Exploit likelihood jumped
  4. Record last updated
How EdgeProtect ranks it
86out of 100Critical

CVE-2022-2068 scores 86. Action: Patch immediately.

We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:

  • Evidence it is being exploitedBiggest factor
  • How severe it isStrong factor
  • How widely exposed it isKey context
  • Real threat activity around itKey context

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.

When CVE-2022-2068 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2022-2068? 28 products.

The published record lists 28 products from 6 vendors. Versions are shown as published: "1.0.2 to before 1.0.2zf" means from 1.0.2 up to, but not including, 1.0.2zf. If you run one of these, check your version, then go to the fix below.

Remediation

How do I fix CVE-2022-2068? Four steps.

  1. Check whether you run itCompare your versions with the affected products above. Not sure what you run? EdgeProtect can work it out from your public website, or you can pick it from a list.
  2. Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisories and patch notes first in the list.
  3. If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
  4. Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

References

11 links
EdgeProtect

Does CVE-2022-2068 affect you? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2022-2068 is a high-severity flaw in OpenSSL, published on 21 June 2022. An attacker has to be already on the device with an ordinary user account, but a person has to take an action first. If it works, the attacker can read data, change data and take it offline.

It scores 7.3 out of 10 on the CVSS severity scale, which is high. Our risk score for CVE-2022-2068 is 86 out of 100, which is Critical. Its action is "Patch immediately". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 96%. That can change at any time, which is why we keep watching.

For OpenSSL: 1.0.2 to before 1.0.2zf, 1.1.1 to before 1.1.1p, 3.0.0 to before 3.0.4. The record lists 28 products in all, each with its versions, under "Who is affected" on this page.

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

Keep exploring