CVE-2023-49800 Vulnerability Analysis & Exploit Details

CVE-2023-49800
Vulnerability Scoring

7.5
/10
Very High Risk

Highly exploitable, CVE-2023-49800 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-2023-49800 Details

Status: Modified

Last updated: 🕣 21 Nov 2024, 08:33 UTC
Originally published on: 🕛 09 Dec 2023, 00:15 UTC

Time between publication and last update: 348 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-2023-49800 Vulnerability Summary

CVE-2023-49800: `nuxt-api-party` is an open source module to proxy API requests. The library allows the user to send many options directly to `ofetch`. There is no filter on which options are available. We can abuse the retry logic to cause the server to crash from a stack overflow. fetchOptions are obtained directly from the request body. A malicious user can construct a URL known to not fetch successfully, then set the retry attempts to a high value, this will cause a stack overflow as ofetch error handling works recursively resulting in a denial of service. This issue has been addressed in version 0.22.1. Users are advised to upgrade. Users unable to upgrade should limit ofetch options.

Assessing the Risk of CVE-2023-49800

Access Complexity Graph

The exploitability of CVE-2023-49800 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-2023-49800

With low attack complexity and no required privileges, CVE-2023-49800 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-2023-49800, 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-2023-49800, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: None
    CVE-2023-49800 has no significant impact on data confidentiality.
  • Integrity: None
    CVE-2023-49800 poses no threat to data integrity.
  • Availability: High
    CVE-2023-49800 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.063% (probability of exploit)

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

CVE-2023-49800 References

External References

CWE Common Weakness Enumeration

CWE-787

Vulnerable Configurations

  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.1.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.4.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.4.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.4.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.4.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.4.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.4.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.4.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.4.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.5.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.5.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.5.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.5.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.5.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.5.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.5.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.5.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.5.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.5.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.5.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.5.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.6.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.6.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.6.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.6.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.6.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.6.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.6.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.6.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.6.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.6.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.6.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.6.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.7.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.7.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.7.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.7.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.7.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.7.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.8.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.8.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.8.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.8.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.8.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.8.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.9.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.9.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.9.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.9.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.9.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.9.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.9.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.9.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.9.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.9.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.10.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.10.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.10.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.10.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.10.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.10.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.10.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.10.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.10.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.10.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.10.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.10.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.11.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.11.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.11.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.11.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.11.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.11.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.11.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.11.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.11.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.11.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.12.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.12.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.13.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.13.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.13.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.13.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.14.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.14.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.14.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.14.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.14.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.14.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.14.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.14.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.15.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.15.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.15.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.15.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.15.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.15.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.15.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.15.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.15.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.15.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.16.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.16.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.16.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.16.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.16.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.16.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.16.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.16.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.16.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.16.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.17.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.17.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.17.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.17.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.18.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.18.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.18.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.18.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.19.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.19.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.20.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.20.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.20.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.20.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.21.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.21.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.21.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.21.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.21.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.21.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:johannschopplich:nuxt_api_party:0.21.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:johannschopplich:nuxt_api_party:0.21.3:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2023-49800: 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-3805 – A vulnerability classified as critical was found in sarrionandia tournatrack up to 4c13a23f43da5317eea4614870a7a8510fc540ec. Affected by this vulne...
  • CVE-2025-3804 – A vulnerability classified as critical has been found in thautwarm vscode-diana 0.0.1. Affected is an unknown function of the file Gen.py of the co...
  • CVE-2025-3803 – A vulnerability was found in Tenda W12 and i24 3.0.0.4(2887)/3.0.0.5(3644). It has been rated as critical. This issue affects the function cgiSysSc...
  • CVE-2025-3802 – A vulnerability was found in Tenda W12 and i24 3.0.0.4(2887)/3.0.0.5(3644). It has been declared as critical. This vulnerability affects the functi...
  • CVE-2025-3801 – A vulnerability was found in songquanpeng one-api up to 0.6.10. It has been classified as problematic. This affects an unknown part of the componen...