CVE-2022-1292

Public on

Last Modified: UTC

Moderate Moderate Impact What does this mean?
6.7 CVSS v3 Base Score

Description

A flaw was found in OpenSSL. The c_rehash script does not properly sanitize shell meta-characters to prevent command injection. Some operating systems distribute this script in a manner where it is automatically executed. This flaw allows an attacker to execute arbitrary commands with the privileges of the script on these operating systems.

Statement

Red Hat Enterprise Linux uses a system-wide store of trusted certificates bundled in a single file and updated via update-ca-trust. The c_rehash script is not included in the default installation on any supported RHEL version, and is never executed automatically. For these reasons, this flaw has been rated as having a security impact of Moderate.

Red Hat Enterprise Linux 7 provides a vulnerable version of the c_rehash script in the openssl-perl package, available only through the unsupported Optional repository. As the Optional repository is not supported and Red Hat Enterprise Linux 7 is in Maintenance Support 2 Phase, this issue is not planned to be addressed there.

Red Hat Satellite ships an affected version of the c_rehash script embedded in puppet-agent package, however, the product is not vulnerable since it does not execute scripts with untrusted data. Moreover, the scriplet is owned by root user and is supposed to be accessed only by administrators.

Red Hat updates the OpenSSL compatibility packages (compat-openssl) to only address Important or Critical security issues with backported security patches.

Mitigation

As mentioned in the upstream security advisory, use of the c_rehash script is considered obsolete and should be replaced by the OpenSSL rehash command line tool.

Additional Information

External References

Content from www.cve.org is not included.https://www.cve.org/CVERecord?id=CVE-2022-1292

Content from nvd.nist.gov is not included.https://nvd.nist.gov/vuln/detail/CVE-2022-1292

Content from www.openssl.org is not included.https://www.openssl.org/news/secadv/20220503.txt

Affected Packages and Issued Red Hat Security Errata

Products / Services Components State Errata
JBoss Core Services for RHEL 8 jbcs-httpd24-openssl Fixed RHSA-2022:8840
JBoss Core Services on RHEL 7 jbcs-httpd24-openssl Fixed RHSA-2022:8840
JWS 5.7.1 release openssl Fixed RHSA-2022:8913
Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/management-ingress-rhel8 Not affected
Red Hat Enterprise Linux 6 openssl Out of support scope
Red Hat Enterprise Linux 6 openssl098e Out of support scope
Red Hat Enterprise Linux 7 openssl Out of support scope
Red Hat Enterprise Linux 7 openssl098e Out of support scope
Red Hat Enterprise Linux 7 ovmf Out of support scope
Red Hat Enterprise Linux 8 openssl Fixed RHSA-2022:5818
Unless explicitly stated as not affected, all previous versions of packages in any minor update stream of a product listed here should be assumed vulnerable, although may not have been subject to full analysis.

Common Vulnerability Scoring System (CVSS) Score Details

Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authorities (CNA) source for its products and services (see Red Hat classifications ).

CVSS v3 Score Breakdown Red Hat NVD
CVSS v3 Base Score 6.7 7.3
Attack Vector Local Local
Attack Complexity Low Low
Privileges Required High Low
User Interaction None Required
Scope Unchanged Unchanged
Confidentiality Impact High High
Integrity Impact High High
Availability Impact High High

CVSS v3 Vector

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

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

Red Hat CVSS v3 Score Explanation

The command injection relies on the script processing a specially crafted certificate on the file system. There is no way to run the script over the network in Red Hat Enterprise Linux. As a result, Red Hat has set the Attack Vector to Local and Privileged Required to High as the script requires write permissions to the system-wide store location and the attacker needs to first create such a file.

Acknowledgements

Upstream acknowledges Elison Niven (Sophos) as the original reporter.

Frequently Asked Questions

Why is Red Hat's CVSS v3 score or Impact different from other vendors?

 For open source software shipped by multiple vendors, the CVSS base scores may vary for each vendor's version depending on the version they ship, how they ship it, the platform, and even how the software is compiled. This makes scoring of vulnerabilities difficult for third-party vulnerability databases such as NVD that only provide a single CVSS base score for each vulnerability. Red Hat scores reflect how a vulnerability affects our products specifically.

For more information, see https://access.redhat.com/solutions/762393.

My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
  • "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
  • "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.

What can I do if my product is listed as "Will not fix"?

 A "will not fix" status means that a fix for an affected product version is not planned or not possible due to complexity, which may create additional risk.

Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
  • Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
  • Apply a mitigation (if one exists).
  • Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.

What can I do if my product is listed as "Fix deferred"?

 A deferred status means that a fix for an affected product version is not guaranteed due to higher-priority development work.

Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
  • Apply a mitigation (if one exists).
  • Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
  • Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.

What is a mitigation?

 A mitigation is an action that can be taken to reduce the impact of a security vulnerability, without deploying any fixes.

I have a Red Hat product but it is not in the above list, is it affected?

 The listed products were found to include one or more of the components that this vulnerability affects. These products underwent a thorough evaluation to determine their affectedness by this vulnerability. Note that layered products (such as container-based offerings) that consume affected components from any of the products listed in this table may be affected and are not represented.

Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?

 In order to maintain code stability and compatibility, Red Hat usually does not rebase packages to entirely new versions. Instead, we backport fixes and new features to an older version of the package we distribute. This can result in some security scanners that only consider the package version to report the package as vulnerable. To avoid this, we suggest that you use an approved vulnerability scanner from our This content is not included.Red Hat Vulnerability Scanner Certification program.

My product is listed as "Out of Support Scope". What does this mean?

 When a product is listed as "Out of Support Scope", it means a vulnerability with the impact level assigned to this CVE is no longer covered by its current support lifecycle phase. The product has been identified to contain the impacted component, but analysis to determine whether it is affected or not by this vulnerability was not performed. The product should be assumed to be affected. Customers are advised to apply any mitigation options documented on this page, consider removing or disabling the impacted component, or upgrade to a supported version of the product that has an update available.