HIGH CVSS 7.1
Published: 2022-09-19

CVE-2022-2995

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

CyberVault Technical Summary

Analyst Synthesis

Technical analysis, exploit verification, and patch instructions for CVE-2022-2995 impacting kubernetes cri-o. Evaluated with CVSS Base Score of 7.1 (HIGH).

Original NVD Description

Source: NIST NVD
Incorrect handling of the supplementary groups in the CRI-O container engine might lead to sensitive information disclosure or possible data modification if an attacker has direct access to the affected container where supplementary groups are used to set access permissions and is able to execute a binary code in that container.

📊 CVSS v3.1 Metric Breakdown

Attack Vector
Local (AV:L)
Requires local system execution permissions
Attack Complexity
Low (AC:L)
No specialized conditions required
Privileges Required
Low (PR:L)
Standard user access required
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
High (I:H)
Total modification of target system
Availability
None (A:N)
No system availability impact

🎯 Affected Versions Matrix

Affected Product kubernetes / cri-o
Affected Versions 1.25.0
Weakness Enumeration CWE-284

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-2995 impacting kubernetes cri-o.

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

info:
  name: kubernetes cri-o - Security Advisory & Vulnerability Scan
  author: cybervault-security-intel
  severity: high
  description: |
    Automated signature & scanner for CVE-2022-2995 affecting kubernetes cri-o.
    Evaluation: Incorrect handling of the supplementary groups in the CRI-O container engine might lead to sensitive information disclosure or possible data modificat...
  reference:
    - https://cybervault-cve.pages.dev/cve/CVE-2022-2995
  classification:
    cvss-metrics: CVSS:3.1/CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
    cvss-score: 7.1
    cve-id: CVE-2022-2995
    cwe-id: CWE-284
  tags: cve,cve-2022-2995,kubernetes,cri-o,high

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

import requests
import sys

def verify_vulnerability(target_url):
    print(f"[*] Auditing {target_url} for CVE-2022-2995 (kubernetes cri-o)...")
    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 kubernetes cri-o scope (1.25.0).")
        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-2995.sh
# Recommended Remediation & Patching Commands for CVE-2022-2995
# 1. Update package via distribution package manager:
sudo apt-get update && sudo apt-get --only-upgrade install cri-o 2>/dev/null || \
sudo dnf upgrade cri-o 2>/dev/null || \
sudo yum update cri-o

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

# 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-2995 in kubernetes cri-o?

Review vendor-specific security notices and update kubernetes cri-o 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-2995?

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-2995?

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

Risk Snapshot
7.1
HIGH SEVERITY
CVE ID CVE-2022-2995
Weakness CWE-284
Vendor kubernetes
Product cri-o
Published 2022-09-19
Vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N