CVE-2022-2068

CRITICALNVD 7.39.8▲
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-06-22. NVD baseline CVSS 7.3; sources differ by 2.5.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 96%
  • Public exploit code is available (ssvc poc, epss top5pct, epss high)
CISA-KEV: Not listedEPSS PROB: 96%CVSS: 7.3Exploit: ssvc poc · epss top5pct · epss highExposed: 0

A fix is available — apply it.

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).

CVSS v3
7.3
EG Score
9.8(medium)
EG Risk
97(Attend)
EG Risk 97/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation96% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
96%
EPSS %ILE
100%
KEV
Not listed

Published

June 21, 2022

Last Modified

November 3, 2025

References (20)

Vendor Advisories for CVE-2022-2068(11)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl (1.0.1f-1ubuntu2.27+esm10) @ trusty2026-05-25ubuntu
ubuntulibssl3 (3.0.2-0ubuntu1.5) @ jammy2026-05-25ubuntu
ubuntulibssl1.0.0 (1.0.2g-1ubuntu4.20+esm5) @ xenial2026-05-25ubuntu
ubuntunodejs-doc (12.22.9~dfsg-1ubuntu3.1) @ jammy2026-05-25ubuntu
redhatpuppet-agent-0:7.26.0-3.el8sat2023-11-08redhat
redhatpuppet-agent-0:7.26.0-3.el9sat2023-10-20redhat
redhatjws5-tomcat-native-0:1.2.31-11.redhat_11.el9jws2022-12-12redhat
redhatopenssl2022-12-12redhat
redhatjbcs-httpd24-openssl-1:1.1.1k-13.el7jbcs2022-12-08redhat
redhatpatch2022-12-08redhat
redhatopenssl-1:3.0.1-41.el9_02022-08-30redhat
redhatopenssl-1:1.1.1k-7.el8_62022-08-03redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:10(1)
PackageVulnerable rangeFixed inDependents
openssl1.1.1c-1 ... 1.1.1n-0+deb10u2 (24 versions)1.1.1n-0+deb10u3—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
openssl1.1.1k-1 ... 1.1.1n-0+deb11u2 (8 versions)1.1.1n-0+deb11u3—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssl—3.0.4-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl—3.0.4-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl—3.0.4-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 2× in last 7d / 6× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-24 14:13 UTCEPSS rescore
  2. 2026-08-23 00:16 UTCEPSS rescore
  3. 2026-08-18 22:10 UTCOSV refresh
  4. 2026-08-16 14:53 UTCEPSS rescore
  5. 2026-08-12 13:48 UTCEPSS rescore
  6. 2026-08-03 17:57 UTCOSV refresh
  7. 2026-07-25 14:15 UTCEPSS rescore
  8. 2026-07-23 02:07 UTCEG score recompute
  9. 2026-07-22 22:54 UTCEG score recompute
  10. 2026-07-22 14:06 UTCEPSS rescore
  11. 2026-07-22 14:06 UTCEPSS rescore
  12. 2026-07-21 15:22 UTCEPSS rescore
  13. 2026-07-21 15:22 UTCEPSS rescore
  14. 2026-07-17 06:24 UTCOSV refresh
  15. 2026-07-13 06:11 UTCEPSS rescore
  16. 2026-07-13 06:11 UTCEPSS rescore
  17. 2026-07-07 13:44 UTCEPSS rescore
  18. 2026-06-29 04:32 UTCOSV refresh
  19. 2026-06-22 14:24 UTCEPSS rescore
  20. 2026-06-22 14:24 UTCEPSS rescore
  21. 2026-06-21 01:58 UTCEPSS rescore
  22. 2026-06-21 01:58 UTCEPSS rescore
  23. 2026-06-15 17:46 UTCEPSS rescore
  24. 2026-06-14 23:15 UTCEPSS rescore
  25. 2026-06-13 22:58 UTCEPSS rescore
Show 39 more
  1. 2026-06-12 23:10 UTCEPSS rescore
  2. 2026-06-12 23:10 UTCEPSS rescore
  3. 2026-06-11 23:26 UTCOSV refresh
  4. 2026-06-11 13:58 UTCEPSS rescore
  5. 2026-06-11 13:58 UTCEPSS rescore
  6. 2026-06-10 22:16 UTCEPSS rescore
  7. 2026-06-10 13:20 UTCEPSS rescore
  8. 2026-06-08 14:15 UTCEPSS rescore
  9. 2026-06-08 14:15 UTCEPSS rescore
  10. 2026-06-07 15:23 UTCEPSS rescore
  11. 2026-06-07 15:23 UTCEPSS rescore
  12. 2026-06-07 15:23 UTCEPSS rescore
  13. 2026-06-06 13:46 UTCEPSS rescore
  14. 2026-06-06 13:46 UTCEPSS rescore
  15. 2026-06-05 22:45 UTCEPSS rescore
  16. 2026-06-05 22:45 UTCEPSS rescore
  17. 2026-06-04 13:11 UTCEPSS rescore
  18. 2026-06-04 13:11 UTCEPSS rescore
  19. 2026-06-02 20:11 UTCEPSS rescore
  20. 2026-06-02 20:11 UTCEPSS rescore
  21. 2026-06-02 20:11 UTCEPSS rescore
  22. 2026-06-01 13:50 UTCEPSS rescore
  23. 2026-06-01 13:50 UTCEPSS rescore
  24. 2026-05-31 22:29 UTCEPSS rescore
  25. 2026-05-31 22:29 UTCEPSS rescore
  26. 2026-05-31 22:29 UTCEPSS rescore
  27. 2026-05-31 00:15 UTCEPSS rescore
  28. 2026-05-31 00:15 UTCEPSS rescore
  29. 2026-05-29 13:43 UTCEPSS rescore
  30. 2026-05-29 13:42 UTCEPSS rescore
  31. 2026-05-28 13:43 UTCEPSS rescore
  32. 2026-05-28 13:43 UTCEPSS rescore
  33. 2026-05-28 13:43 UTCEPSS rescore
  34. 2026-05-27 13:39 UTCEPSS rescore
  35. 2026-05-27 13:39 UTCEPSS rescore
  36. 2026-05-25 20:05 UTCEG score recompute
  37. 2026-05-25 20:05 UTCVendor advisory
  38. 2026-05-25 20:05 UTCGHSA enrichment
  39. 2026-05-24 16:51 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-2068?
CVE-2022-2068 is a critical vulnerability published on June 21, 2022. In addition to the crehash shell command injection identified in CVE-2022-1292, further circumstances where the crehash 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…
When was CVE-2022-2068 disclosed?
CVE-2022-2068 was first published in the National Vulnerability Database on June 21, 2022, with the most recent update on November 3, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-2068 actively exploited?
CVE-2022-2068 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96% probability of exploitation in the next 30 days, which ranks it in the top 0.1% of all scored CVEs.
What is the CVSS score of CVE-2022-2068?
CVE-2022-2068 has a CVSS v3 base score of 7.3 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.8.
How do I remediate CVE-2022-2068?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-2068, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-2068

Explore →

Is Your Infrastructure Affected by CVE-2022-2068?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs