CVE-2022-21676 Vulnerability Analysis & Exploit Details

CVE-2022-21676
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2022-21676 poses a critical security risk that could lead to severe breaches.

Attack Complexity Details

  • Attack Complexity: Low
    Exploits can be performed without significant complexity or special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: None
    No privileges are required for exploitation.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2022-21676 Details

Status: Modified

Last updated: 🕡 21 Nov 2024, 06:45 UTC
Originally published on: 🕖 12 Jan 2022, 19:15 UTC

Time between publication and last update: 1043 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2022-21676 Vulnerability Summary

CVE-2022-21676: Engine.IO is the implementation of transport-based cross-browser/cross-device bi-directional communication layer for Socket.IO. A specially crafted HTTP request can trigger an uncaught exception on the Engine.IO server, thus killing the Node.js process. This impacts all the users of the `engine.io` package starting from version `4.0.0`, including those who uses depending packages like `socket.io`. Versions prior to `4.0.0` are not impacted. A fix has been released for each major branch, namely `4.1.2` for the `4.x.x` branch, `5.2.1` for the `5.x.x` branch, and `6.1.1` for the `6.x.x` branch. There is no known workaround except upgrading to a safe version.

Assessing the Risk of CVE-2022-21676

Access Complexity Graph

The exploitability of CVE-2022-21676 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2022-21676

With low attack complexity and no required privileges, CVE-2022-21676 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2022-21676, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2022-21676, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2022-21676 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2022-21676 poses no threat to data integrity.
  • Availability: High
    CVE-2022-21676 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.281% (probability of exploit)

EPSS Percentile: 68.74% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 31.260000000000005% of others.

CVE-2022-21676 References

External References

CWE Common Weakness Enumeration

CWE-755

Vulnerable Configurations

  • cpe:2.3:a:socket:engine.io:4.0.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:socket:engine.io:4.0.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:socket:engine.io:4.0.0:alpha0:*:*:*:node.js:*:*
    cpe:2.3:a:socket:engine.io:4.0.0:alpha0:*:*:*:node.js:*:*
  • cpe:2.3:a:socket:engine.io:4.0.0:alpha1:*:*:*:node.js:*:*
    cpe:2.3:a:socket:engine.io:4.0.0:alpha1:*:*:*:node.js:*:*
  • cpe:2.3:a:socket:engine.io:4.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:socket:engine.io:4.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:socket:engine.io:4.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:socket:engine.io:4.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:socket:engine.io:4.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:socket:engine.io:4.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:socket:engine.io:4.0.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:socket:engine.io:4.0.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:socket:engine.io:4.0.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:socket:engine.io:4.0.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:socket:engine.io:4.0.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:socket:engine.io:4.0.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:socket:engine.io:4.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:socket:engine.io:4.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:socket:engine.io:4.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:socket:engine.io:4.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:socket:engine.io:5.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:socket:engine.io:5.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:socket:engine.io:5.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:socket:engine.io:5.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:socket:engine.io:5.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:socket:engine.io:5.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:socket:engine.io:5.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:socket:engine.io:5.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:socket:engine.io:6.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:socket:engine.io:6.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:socket:engine.io:6.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:socket:engine.io:6.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:socket:engine.io:6.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:socket:engine.io:6.1.0:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2022-21676: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2025-4208 – The NEX-Forms – Ultimate Form Builder – Contact forms and much more plugin for WordPress is vulnerable to Limited Code Execution in all versions up...
  • CVE-2025-3862 – Contest Gallery plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the ‘id’ parameter in all versions up to, and including, 26.0...
  • CVE-2025-3506 – Files to be deployed with agents are accessible without authentication in Checkmk 2.1.0, Checkmk 2.2.0, Checkmk 2.3.0 and <Checkmk 2.4.0b6 allows a...
  • CVE-2025-3468 – The NEX-Forms – Ultimate Form Builder – Contact forms and much more plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the clean...
  • CVE-2025-2806 – The tagDiv Composer plugin for WordPress, used by the Newspaper theme, is vulnerable to Reflected Cross-Site Scripting via the ‘data’ parameter in ...