CVE-2022-2068 [High] | Command Injection in Openssl

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

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-05-13	18.58%	20.22%	+1.64%
2	2026-03-27	18.75%	18.58%	-0.17%
3	2026-03-22	—	18.75%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-05-13

18.58%

20.22%

+1.64%

2026-03-27

18.75%

18.58%

-0.17%

2026-03-22

—

18.75%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.3	3.1	HIGH	`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:L) They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:R) A real person has to do something—click, install, enable—otherwise it doesn’t land. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	1.3	5.9	[email protected]
9.8	3.1	CRITICAL	`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:N) No account or special rights needed—anonymous or random user is enough. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:H) They could widely tamper with or forge data—trust in the data is badly hurt. Availability (A:H) Could take the service down hard or make it unusable for people who depend on it.	3.9	5.9	134c704f-9b21-4f2e-91b3-4a467353bcc0
10.0	2.0	HIGH	`AV:N/AC:L/Au:N/C:C/I:C/A:C` Click to expand Access vector (AV:N) Can be exploited remotely over network reachability. Access complexity (AC:L) Exploitation conditions are straightforward and predictable. Authentication (AU:N) No authentication is required. Confidentiality impact (C:C) Complete confidentiality impact. Integrity impact (I:C) Complete integrity impact. Availability impact (A:C) Complete availability impact.	10.0	10.0	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.3

3.1

HIGH

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:L): They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:R): A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

1.3

5.9

[email protected]

9.8

3.1

CRITICAL

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N): No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:H): They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H): Could take the service down hard or make it unusable for people who depend on it.

3.9

5.9

134c704f-9b21-4f2e-91b3-4a467353bcc0

10.0

2.0

HIGH

AV:N/AC:L/Au:N/C:C/I:C/A:C Click to expand

Access vector (AV:N): Can be exploited remotely over network reachability.
Access complexity (AC:L): Exploitation conditions are straightforward and predictable.
Authentication (AU:N): No authentication is required.
Confidentiality impact (C:C): Complete confidentiality impact.
Integrity impact (I:C): Complete integrity impact.
Availability impact (A:C): Complete availability impact.

10.0

[email protected]

OS Trackers for CVE-2022-2068

vendor	priority	summary	link
`alpine`	—	CVE-2022-2068: 1 source package rows (openssl); 1 state rows across 1 repos (edge-main); fixed 1, open 0.	https://security.alpinelinux.org/vuln/CVE-2022-2068
`debian`	not yet assigned	CVE-2022-2068 not yet assigned priority: Debian including 1 source packages (openssl), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-2068
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2022-2068
`suse`	medium	CVE-2022-2068 severity moderate: SUSE including 618 source package names (0.23.0.3.2.201:libopenssl1_1-1.1.1d-150200.11.48.1, 0.23.0.3.2.201:libopenssl1_1-hmac-1.1.1d-150200.11.48.1, …), 1729 product×package rows across 312 product lines (Container bci/bci-init, Container bci/dotnet-aspnet, … (312 product lines)): Fixed 1288, Known Not Affected 371, Known Affected 70.	https://www.suse.com/security/cve/CVE-2022-2068/
`ubuntu`	medium	CVE-2022-2068 medium priority: Ubuntu including 4 source packages (edk2, nodejs, openssl, openssl1.0), 56 status rows across 14 suites (bionic, focal, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): not-affected 30, DNE 13, released 9, needs-triage 4.	https://ubuntu.com/security/CVE-2022-2068

Affected software / configurations for CVE-2022-2068

Vendor	Product	Version	Raw CPE
openssl	openssl	>= 1.0.2, < 1.0.2zf	cpe:2.3:a:openssl:openssl::::::::
openssl	openssl	>= 1.1.1, < 1.1.1p	cpe:2.3:a:openssl:openssl::::::::
openssl	openssl	>= 3.0.0, < 3.0.4	cpe:2.3:a:openssl:openssl::::::::
debian	debian_linux	10.0	cpe:2.3:o:debian:debian_linux:10.0:::::::*
debian	debian_linux	11.0	cpe:2.3:o:debian:debian_linux:11.0:::::::*
fedoraproject	fedora	35	cpe:2.3:o:fedoraproject:fedora:35:::::::*
fedoraproject	fedora	36	cpe:2.3:o:fedoraproject:fedora:36:::::::*
siemens	sinec_ins	< 1.0	cpe:2.3:a:siemens:sinec_ins::::::::
siemens	sinec_ins	1.0	cpe:2.3:a:siemens:sinec_ins:1.0:-::::::
siemens	sinec_ins	1.0	cpe:2.3:a:siemens:sinec_ins:1.0:sp1::::::
siemens	sinec_ins	1.0	cpe:2.3:a:siemens:sinec_ins:1.0:sp2::::::
netapp	element_software	—	cpe:2.3:a:netapp:element_software:-:::::::*
netapp	hci_management_node	—	cpe:2.3:a:netapp:hci_management_node:-:::::::*
netapp	ontap_antivirus_connector	—	cpe:2.3:a:netapp:ontap_antivirus_connector:-:::::::*
netapp	ontap_select_deploy_administration_utility	—	cpe:2.3:a:netapp:ontap_select_deploy_administration_utility:-:::::::*
netapp	santricity_smi-s_provider	—	cpe:2.3:a:netapp:santricity_smi-s_provider:-:::::::*
netapp	smi-s_provider	—	cpe:2.3:a:netapp:smi-s_provider:-:::::::*
netapp	snapmanager	—	cpe:2.3:a:netapp:snapmanager:-:::::hyper-v::
netapp	solidfire	—	cpe:2.3:a:netapp:solidfire:-:::::::*
netapp	bootstrap_os	—	cpe:2.3:o:netapp:bootstrap_os:-:::::::*
netapp	h615c_firmware	—	cpe:2.3:o:netapp:h615c_firmware:-:::::::*
netapp	h610s_firmware	—	cpe:2.3:o:netapp:h610s_firmware:-:::::::*
netapp	h610c_firmware	—	cpe:2.3:o:netapp:h610c_firmware:-:::::::*
netapp	h410c_firmware	—	cpe:2.3:o:netapp:h410c_firmware:-:::::::*
netapp	h300s_firmware	—	cpe:2.3:o:netapp:h300s_firmware:-:::::::*
netapp	h500s_firmware	—	cpe:2.3:o:netapp:h500s_firmware:-:::::::*
netapp	h700s_firmware	—	cpe:2.3:o:netapp:h700s_firmware:-:::::::*
netapp	h410s_firmware	—	cpe:2.3:o:netapp:h410s_firmware:-:::::::*
netapp	fas_8300_firmware	—	cpe:2.3:o:netapp:fas_8300_firmware:-:::::::*
netapp	fas_8700_firmware	—	cpe:2.3:o:netapp:fas_8700_firmware:-:::::::*
netapp	fas_a400_firmware	—	cpe:2.3:o:netapp:fas_a400_firmware:-:::::::*
netapp	aff_8300_firmware	—	cpe:2.3:o:netapp:aff_8300_firmware:-:::::::*
netapp	aff_8700_firmware	—	cpe:2.3:o:netapp:aff_8700_firmware:-:::::::*
netapp	aff_a400_firmware	—	cpe:2.3:o:netapp:aff_a400_firmware:-:::::::*
broadcom	sannav	—	cpe:2.3:a:broadcom:sannav:-:::::::*

References for CVE-2022-2068

URL	Tags
https://cert-portal.siemens.com/productcert/pdf/ssa-332410.pdf	Third Party Advisory
https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=2c9c35870601b4a44d86ddbf512b38df38285cfa	Patch
https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=7a9c027159fe9e1bbc2cd38a8a2914bff0d5abd9	Patch
https://git.openssl.org/gitweb/?p=openssl.git%3Ba=commitdiff%3Bh=9639817dac8bbbaa64d09efad7464ccc405527c7	Patch
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/6WZZBKUHQFGSKGNXXKICSRPL7AMVW5M5/	Mailing List Third Party Advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/VCMNWKERPBKOEBNL7CLTTX3ZZCZLH7XA/	Mailing List Third Party Advisory
https://security.netapp.com/advisory/ntap-20220707-0008/	Third Party Advisory
https://www.debian.org/security/2022/dsa-5169	Third Party Advisory
https://www.openssl.org/news/secadv/20220621.txt	Vendor Advisory
http://seclists.org/fulldisclosure/2024/Nov/0
https://gitlab.com/fraf0/cve-2022-1292-re_score-analysis

URL

CVE-2022-2068 | The c_rehash script allows command injection

Exploit prediction scoring system (EPSS) score for CVE-2022-2068

Common vulnerability scoring system (CVSS) metrics for CVE-2022-2068

Weakness enumeration for CVE-2022-2068

OS Trackers for CVE-2022-2068

Affected software / configurations for CVE-2022-2068

References for CVE-2022-2068