CVE-2021-23386 Vulnerability Analysis & Exploit Details

CVE-2021-23386
Vulnerability Scoring

7.7
/10
Very High Risk

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

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Changed
    Successful exploitation can impact components beyond the vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2021-23386 Details

Status: Modified

Last updated: 🕠 21 Nov 2024, 05:51 UTC
Originally published on: 🕔 20 May 2021, 17:15 UTC

Time between publication and last update: 1280 days

CVSS Release: version 3

CVSS3 Source

report@snyk.io

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2021-23386 Vulnerability Summary

CVE-2021-23386: This affects the package dns-packet before 5.2.2. It creates buffers with allocUnsafe and does not always fill them before forming network packets. This can expose internal application memory over unencrypted network when querying crafted invalid domain names.

Assessing the Risk of CVE-2021-23386

Access Complexity Graph

The exploitability of CVE-2021-23386 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-2021-23386

This vulnerability, CVE-2021-23386, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate risks.

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-2021-23386, 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-2021-23386, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: High
    Exploiting CVE-2021-23386 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: Low
    Exploiting CVE-2021-23386 may cause minor changes to data without severely impacting its accuracy.
  • Availability: Low
    CVE-2021-23386 may slightly degrade system performance without fully affecting service availability.

Exploit Prediction Scoring System (EPSS)

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

EPSS Score: 0.097% (probability of exploit)

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

CVE-2021-23386 References

External References

CWE Common Weakness Enumeration

CWE-909

Vulnerable Configurations

  • cpe:2.3:a:dns-packet_project:dns-packet:-:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:-:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:1.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:1.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:1.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:1.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:1.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:1.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:1.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:1.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:1.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:1.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:1.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:1.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:1.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:1.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:1.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:1.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:1.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:1.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:1.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:1.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:1.3.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:1.3.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:1.3.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:1.3.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:2.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:2.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:3.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:3.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:3.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:3.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:4.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:4.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:4.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:4.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:4.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:4.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:4.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:4.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:5.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:5.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:5.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:5.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:5.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:5.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:5.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:5.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:5.0.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:5.0.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:5.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:5.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:5.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:5.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:5.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:5.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:5.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:5.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:dns-packet_project:dns-packet:5.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:dns-packet_project:dns-packet:5.2.1:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2021-23386: 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-5301 – ONLYOFFICE Docs (DocumentServer) in versions equal and below 8.3.1 are affected by a reflected cross-site scripting (XSS) issue when opening files ...
  • CVE-2025-40592 – A vulnerability has been identified in Mendix Studio Pro 10 (All versions < V10.23.0), Mendix Studio Pro 10.12 (All versions < V10.12.17), Mendix S...
  • CVE-2025-5012 – The Workreap plugin for WordPress, used by the Workreap - Freelance Marketplace WordPress Theme, is vulnerable to arbitrary file uploads due to mis...
  • CVE-2025-4973 – The Workreap plugin for WordPress, used by the Workreap - Freelance Marketplace WordPress Theme, is vulnerable to authentication bypass in all vers...
  • CVE-2025-35978 – Improper restriction of communication channel to intended endpoints issue exists in UpdateNavi V1.4 L10 to L33 and UpdateNaviInstallService Service...