CVE-2023-49583 Vulnerability Analysis & Exploit Details

CVE-2023-49583
Vulnerability Scoring

9.1
/10
Critical Risk

As a catastrophic security flaw, CVE-2023-49583 has severe implications, demanding immediate intervention.

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-49583 Details

Status: Modified

Last updated: 🕣 21 Nov 2024, 08:33 UTC
Originally published on: 🕑 12 Dec 2023, 02:15 UTC

Time between publication and last update: 345 days

CVSS Release: version 3

CVSS3 Source

cna@sap.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2023-49583 Vulnerability Summary

CVE-2023-49583: SAP BTP Security Services Integration Library ([Node.js] @sap/xssec - versions < 3.6.0, allow under certain conditions an escalation of privileges. On successful exploitation, an unauthenticated attacker can obtain arbitrary permissions within the application.

Assessing the Risk of CVE-2023-49583

Access Complexity Graph

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

With low attack complexity and no required privileges, CVE-2023-49583 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-49583, 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-49583, 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-2023-49583 can result in unauthorized access to sensitive data, severely compromising data privacy.
  • Integrity: High
    CVE-2023-49583 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: None
    CVE-2023-49583 does not impact system 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.301% (probability of exploit)

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

CVE-2023-49583 References

External References

CWE Common Weakness Enumeration

CWE-749

CAPEC Common Attack Pattern Enumeration and Classification

  • WebView Injection CAPEC-500 An adversary, through a previously installed malicious application, injects code into the context of a web page displayed by a WebView component. Through the injected code, an adversary is able to manipulate the DOM tree and cookies of the page, expose sensitive information, and can launch attacks against the web application from within the web page.

Vulnerable Configurations

  • cpe:2.3:a:sap:\@sap\/xssec:1.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:1.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:1.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:1.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:1.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:1.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:1.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:1.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:1.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:1.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.1.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.1.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.1.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.1.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.1.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.1.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.1.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.1.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.1.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.1.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.1.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.1.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.1.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.1.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.1.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.1.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.1.11:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.1.11:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.1.12:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.1.12:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.1.14:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.1.14:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.1.15:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.1.15:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.1.16:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.1.16:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.1.17:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.1.17:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.2.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.2.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.2.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.2.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:2.2.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:2.2.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.0.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.0.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.0.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.0.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.0.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.0.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.0.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.0.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.0.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.0.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.0.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.0.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.0.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.0.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.1.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.1.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.1.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.1.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.2.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.2.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.2.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.2.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.2.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.2.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.2.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.2.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.2.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.2.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.2.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.2.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.2.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.2.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.2.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.2.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.2.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.2.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.2.11:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.2.11:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.2.12:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.2.12:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.2.13:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.2.13:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.2.14:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.2.14:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.2.15:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.2.15:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.2.17:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.2.17:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.2.18:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.2.18:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.3.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.3.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.3.3:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.3.3:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.3.4:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.3.4:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.3.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.3.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:sap:\@sap\/xssec:3.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:sap:\@sap\/xssec:3.5.0:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2023-49583: 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-2130 – A vulnerability was found in OpenXE up to 1.12. It has been declared as problematic. This vulnerability affects unknown code of the component Ticke...
  • CVE-2025-26205 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in mainpositionTV in ltable.c. NOTE: this is dispute...
  • CVE-2025-26204 – Lua 5.4.7, when the debug library is used, has a out-of-bounds read and segmentation violation in equalkey in ltable.c. NOTE: this is disputed beca...
  • CVE-2025-2129 – A vulnerability was found in Mage AI 0.9.75. It has been classified as problematic. This affects an unknown part. The manipulation leads to insecur...
  • CVE-2025-2127 – A vulnerability was found in JoomlaUX JUX Real Estate 3.4.0 on Joomla. It has been classified as problematic. Affected is an unknown function of th...