dbcve.org
OpenSSLFramework / library

CVE-2022-1292

HIGH · 7.3 CVSS v3.1 Published 2022-05-03
Fix available
A fix is available. Upgrade to 1.0.2ze / 1.1.1o or later.
See remediation →
73/100
Remediation priority · Elevated
High EPSS

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
The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. 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.3 (Affected 3.0.0,3.0.1,3.0.2). Fixed in OpenSSL 1.1.1o (Affected 1.1.1-1.1.1n). Fixed in OpenSSL 1.0.2ze (Affected 1.0.2-1.0.2zd).

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

The c_rehash script, distributed with OpenSSL installations, contains a command injection vulnerability due to improper sanitisation of shell metacharacters. An attacker with the ability to control input processed by the script can execute arbitrary commands with the privileges of the script execution context.

MitigationReplace the obsolete c_rehash script with the OpenSSL rehash command-line tool and upgrade to a patched OpenSSL version (3.0.3+, 1.1.1o+, or 1.0.2ze+) on all affected systems.

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.2ze>= 1.1.1, < 1.1.1o>= 3.0.0, < 3.0.3
Debian LinuxOperating system
Affected:= 9.0= 10.0= 11.0
FedoraOperating system
Affected:= 35= 36
Brownfield Connectivity GatewayApplication
Affected:< 2.15
Active Iq Unified ManagerApplication
Affected:all versions
Clustered Data OntapApplication
Affected:all versions
Clustered Data Ontap Antivirus ConnectorApplication
Affected:all versions
Oncommand InsightApplication
Affected:all versions

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
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 installed OpenSSL version
    Run 'openssl version' to see the version number
    Affected if The version falls in these ranges: >= 1.0.2 and < 1.0.2ze, OR >= 1.1.1 and < 1.1.1o, OR >= 3.0.0 and < 3.0.3
  2. Locate the c_rehash script
    Search for c_rehash in common binary directories such as /usr/bin, /usr/local/bin, or by running 'which c_rehash'
    Affected if The c_rehash script exists on the system and the OpenSSL version is vulnerable as determined above
  3. Verify c_rehash is executable
    Check file permissions with 'ls -la' on the c_rehash script path
    Affected if The script has execute permissions and is present on a vulnerable OpenSSL version
  4. Check if c_rehash is invoked in any scripts or automation
    Search for references to c_rehash in shell scripts, cron jobs, or configuration files using grep or similar tools
    Affected if Any automated process calls or references c_rehash on a vulnerable OpenSSL version

A system is affected if it runs a vulnerable OpenSSL version (1.0.2 through 1.0.2zd, 1.1.1 through 1.1.1n, or 3.0.0 through 3.0.2) AND has the c_rehash script present and executable.

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.2ze / 1.1.1o / 2.15 or later
Fixed in 1.0.2ze1.1.1o2.15
Interim mitigation

Replace the obsolete c_rehash script with the OpenSSL rehash command-line tool and upgrade to a patched OpenSSL version (3.0.3+, 1.1.1o+, or 1.0.2ze+) on all affected systems.

Recommended fix High confidence

OpenSSL 3.0.3, 1.1.1o, or 1.0.2ze (depending on your current major version)

  1. Identify the current OpenSSL version installed using: openssl version -a
  2. For OpenSSL 3.x: Upgrade to version 3.0.3 or later
  3. For OpenSSL 1.1.1: Upgrade to version 1.1.1o or later
  4. For OpenSSL 1.0.2: Upgrade to version 1.0.2ze or later
  5. Alternatively, as recommended in the official description: replace use of the obsolete c_rehash script with the OpenSSL rehash command-line tool
  6. After upgrade, verify the fix by checking that c_rehash is no longer used or that the version is patched: openssl version
Caveat Ensure any scripts or workflows relying on c_rehash are updated to use the rehash command-line tool instead, as c_rehash is obsolete

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1292 — 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-1292 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