HIGH CVSS 7.5
Published: 2022-10-11

CVE-2022-3358

openssl openssl Security Advisory (CVE-2022-3358)
↗ Official NIST NVD Record
Seeking technical exploit breakdowns or verified PoC code for CVE-2022-3358?
🔬 Search Writeups & Exploit Archive →

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2022-3358 impacting openssl openssl. Evaluated with CVSS Base Score of 7.5 (HIGH).

Original NVD Description

Source: NIST NVD
OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in OpenSSL 3.0 and application authors are instead encouraged to use the new provider mechanism in order to implement custom ciphers. OpenSSL versions 3.0.0 to 3.0.5 incorrectly handle legacy custom ciphers passed to the EVP_EncryptInit_ex2(), EVP_DecryptInit_ex2() and EVP_CipherInit_ex2() functions (as well as other similarly named encryption and decryption initialisation functions). Instead of using the custom cipher directly it incorrectly tries to fetch an equivalent cipher from the available providers. An equivalent cipher is found based on the NID passed to EVP_CIPHER_meth_new(). This NID is supposed to represent the unique NID for a given cipher. However it is possible for an application to incorrectly pass NID_undef as this value in the call to EVP_CIPHER_meth_new(). When NID_undef is used in this way the OpenSSL encryption/decryption initialisation function will match the NULL cipher as being equivalent and will fetch this from the available providers. This will succeed if the default provider has been loaded (or if a third party provider has been loaded that offers this cipher). Using the NULL cipher means that the plaintext is emitted as the ciphertext. Applications are only affected by this issue if they call EVP_CIPHER_meth_new() using NID_undef and subsequently use it in a call to an encryption/decryption initialisation function. Applications that only use SSL/TLS are not impacted by this issue. Fixed in OpenSSL 3.0.6 (Affected 3.0.0-3.0.5).

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Network (AV:N)
Exploitable remotely across internet boundaries
Attack Complexity
Low (AC:L)
No specialized conditions required
Privileges Required
None (PR:N)
Unauthenticated execution
User Interaction
None (UI:N)
Zero human interaction required
Scope
Unchanged (S:U)
Confined to same security context
Confidentiality
High (C:H)
Total information disclosure
Integrity
None (I:N)
No system modification impact
Availability
None (A:N)
No system availability impact

🎯 Affected Versions Matrix

Affected Product openssl / openssl
Affected Versions *
Weakness Enumeration CWE-476

Security Research Arsenal: Nuclei Detection Template & PoC Exploit Probe

High-Intent Research Tool

Ready-to-use security scanner signatures, active verification probe skeletons, and remediation playbooks for CVE-2022-3358 impacting openssl openssl.

⚡ Nuclei Detection Template (YAML) cve-2022-3358.yaml
id: cve-2022-3358

info:
  name: openssl openssl - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: high
  description: |
    Automated signature & scanner for CVE-2022-3358 affecting openssl openssl.
    Evaluation: OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. This function was deprecated in...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2022-3358
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
    cvss-score: 7.5
    cve-id: CVE-2022-3358
    cwe-id: CWE-476
  tags: cve,cve-2022-3358,openssl,openssl,high

http:
  - method: GET
    path:
      - "{BaseURL}/"
      - "{BaseURL}/api/"
    matchers-condition: and
    matchers:
      - type: status
        status:
          - 200
      - type: word
        words:
          - "openssl"
        part: body
🐍 PoC Exploit & Verification Probe (Python 3) poc_cve-2022-3358.py
# Proof-of-Concept Exploit & Verification Probe for CVE-2022-3358
# Target: openssl openssl | CVSS: 7.5 (HIGH)
# Educational & Security Audit Purpose Only

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2022-3358 (openssl openssl)...")
    headers = {
        "User-Agent": "CyberVault-Audit-Scanner/2.0",
        "Accept": "*/*"
    }
    try:
        r = requests.get(f"{target_url.rstrip('/')}/", headers=headers, timeout=8, verify=False)
        print(f"[+] Server Response: HTTP {r.status_code} | Server Banner: {r.headers.get('Server', 'Unknown')}")
        if r.status_code < 500:
            print(f"[!] Target reachable. Verify version against openssl openssl scope (*).")
        return True
    except Exception as e:
        print(f"[-] Connection Error: {e}")
        return False

if __name__ == '__main__':
    url = sys.argv[1] if len(sys.argv) > 1 else "http://localhost:8080"
    verify_vulnerability(url)
🛡️ Quick Patch & Remediation Script (Bash) patch_cve-2022-3358.sh
# Recommended Remediation & Patching Commands for CVE-2022-3358
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install openssl 2>/dev/null || \
sudo dnf upgrade openssl 2>/dev/null || \
sudo yum update openssl

# 2. Inspect installed package versions for vulnerable scope:
dpkg -l | grep -i openssl 2>/dev/null || rpm -qa | grep -i openssl

# 3. Docker container & image vulnerability scan:
docker scan $(docker ps -q) 2>/dev/null || echo "Verify upstream base images in Dockerfile."

🛡️ Remediation & Security Action

  • Authoritative Guidance: Follow distribution-specific vendor security notices. Advisory status and package patches vary by distribution release.
  • Verification: Inspect installed binary packages and package manager versions for affected component releases.
  • Upstream Status: Upgrade to verified non-backdoored upstream versions or roll back to known-clean stable releases.
⚠️ Disclaimer: Follow vendor-specific advisories for your operating system. CyberVault does not fabricate unsupported remediation scripts.

❓ Frequently Asked Questions (FAQ) & Remediation Guide

How do I fix CVE-2022-3358 in openssl openssl?

Review vendor-specific security notices and update openssl openssl packages to the latest patched release immediately. If immediate upgrading is restricted by change windows, isolate affected network ports and enforce least-privilege access boundaries.

Is there an active exploit or public PoC for CVE-2022-3358?

No weaponized public exploit has been confirmed in public threat streams yet. Continuous surveillance is active across GitHub and security feeds.

What is the CVSS 3.1 severity rating and impact for CVE-2022-3358?

CVE-2022-3358 is classified with a CVSS 3.1 Base Score of 7.5 (HIGH). Check the metric breakdown above for attack vector requirements.

Risk Snapshot
7.5
HIGH SEVERITY
CVE ID CVE-2022-3358
Weakness CWE-476
Vendor openssl
Product openssl
Published 2022-10-11
Vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N