CVE-2023-26158 Vulnerability Analysis & Exploit Details

CVE-2023-26158
Vulnerability Scoring

8.2
/10
Severe Risk

Cybersecurity professionals consider CVE-2023-26158 an immediate threat requiring urgent mitigation.

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

Status: Modified

Last updated: 🕢 21 Nov 2024, 07:50 UTC
Originally published on: 🕔 08 Dec 2023, 05:15 UTC

Time between publication and last update: 349 days

CVSS Release: version 3

CVSS3 Source

report@snyk.io

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2023-26158 Vulnerability Summary

CVE-2023-26158: All versions of the package mockjs are vulnerable to Prototype Pollution via the Util.extend function due to missing check if the attribute resolves to the object prototype. By adding or modifying attributes of an object prototype, it is possible to create attributes that exist on every object, or replace critical attributes with malicious ones. This can be problematic if the software depends on existence or non-existence of certain attributes, or uses pre-defined attributes of object prototype (such as hasOwnProperty, toString or valueOf). User controlled inputs inside the extend() method of the Mock.Handler, Mock.Random, Mock.RE.Handler or Mock.Util, will allow an attacker to exploit this vulnerability. Workaround By using a denylist of dangerous attributes, this weakness can be eliminated. Add the following line in the Util.extend function: js js if (["__proto__", "constructor", "prototype"].includes(name)) continue js // src/mock/handler.js Util.extend = function extend() { var target = arguments[0] || {}, i = 1, length = arguments.length, options, name, src, copy, clone if (length === 1) { target = this i = 0 } for (; i < length; i++) { options = arguments[i] if (!options) continue for (name in options) { if (["__proto__", "constructor", "prototype"].includes(name)) continue src = target[name] copy = options[name] if (target === copy) continue if (copy === undefined) continue if (Util.isArray(copy) || Util.isObject(copy)) { if (Util.isArray(copy)) clone = src && Util.isArray(src) ? src : [] if (Util.isObject(copy)) clone = src && Util.isObject(src) ? src : {} target[name] = Util.extend(clone, copy) } else { target[name] = copy } } } return target }

Assessing the Risk of CVE-2023-26158

Access Complexity Graph

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

With low attack complexity and no required privileges, CVE-2023-26158 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-26158, 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-26158, 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-26158 has no significant impact on data confidentiality.
  • Integrity: Low
    Exploiting CVE-2023-26158 may cause minor changes to data without severely impacting its accuracy.
  • Availability: High
    CVE-2023-26158 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.059% (probability of exploit)

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

CVE-2023-26158 References

External References

CWE Common Weakness Enumeration

CWE-1321

CAPEC Common Attack Pattern Enumeration and Classification

  • Accessing Functionality Not Properly Constrained by ACLs CAPEC-1 In applications, particularly web applications, access to functionality is mitigated by an authorization framework. This framework maps Access Control Lists (ACLs) to elements of the application's functionality; particularly URL's for web apps. In the case that the administrator failed to specify an ACL for a particular element, an attacker may be able to access it with impunity. An attacker with the ability to access functionality not properly constrained by ACLs can obtain sensitive information and possibly compromise the entire application. Such an attacker can access resources that must be available only to users at a higher privilege level, can access management sections of the application, or can run queries for data that they otherwise not supposed to.
  • Exploiting Incorrectly Configured Access Control Security Levels CAPEC-180 An attacker exploits a weakness in the configuration of access controls and is able to bypass the intended protection that these measures guard against and thereby obtain unauthorized access to the system or network. Sensitive functionality should always be protected with access controls. However configuring all but the most trivial access control systems can be very complicated and there are many opportunities for mistakes. If an attacker can learn of incorrectly configured access security settings, they may be able to exploit this in an attack.
  • Manipulating User-Controlled Variables CAPEC-77 This attack targets user controlled variables (DEBUG=1, PHP Globals, and So Forth). An adversary can override variables leveraging user-supplied, untrusted query variables directly used on the application server without any data sanitization. In extreme cases, the adversary can change variables controlling the business logic of the application. For instance, in languages like PHP, a number of poorly set default configurations may allow the user to override variables.

Vulnerable Configurations

  • cpe:2.3:a:mockjs:mock.js:0.1.5:*:*:*:*:node.js:*:*
    cpe:2.3:a:mockjs:mock.js:0.1.5:*:*:*:*:node.js:*:*
  • cpe:2.3:a:mockjs:mock.js:0.1.6:*:*:*:*:node.js:*:*
    cpe:2.3:a:mockjs:mock.js:0.1.6:*:*:*:*:node.js:*:*
  • cpe:2.3:a:mockjs:mock.js:0.1.7:*:*:*:*:node.js:*:*
    cpe:2.3:a:mockjs:mock.js:0.1.7:*:*:*:*:node.js:*:*
  • cpe:2.3:a:mockjs:mock.js:0.1.8:*:*:*:*:node.js:*:*
    cpe:2.3:a:mockjs:mock.js:0.1.8:*:*:*:*:node.js:*:*
  • cpe:2.3:a:mockjs:mock.js:0.1.9:*:*:*:*:node.js:*:*
    cpe:2.3:a:mockjs:mock.js:0.1.9:*:*:*:*:node.js:*:*
  • cpe:2.3:a:mockjs:mock.js:0.1.10:*:*:*:*:node.js:*:*
    cpe:2.3:a:mockjs:mock.js:0.1.10:*:*:*:*:node.js:*:*
  • cpe:2.3:a:mockjs:mock.js:0.1.11:*:*:*:*:node.js:*:*
    cpe:2.3:a:mockjs:mock.js:0.1.11:*:*:*:*:node.js:*:*
  • cpe:2.3:a:mockjs:mock.js:0.2.0:alpha1:*:*:*:node.js:*:*
    cpe:2.3:a:mockjs:mock.js:0.2.0:alpha1:*:*:*:node.js:*:*
  • cpe:2.3:a:mockjs:mock.js:1.0.0:-:*:*:*:node.js:*:*
    cpe:2.3:a:mockjs:mock.js:1.0.0:-:*:*:*:node.js:*:*
  • cpe:2.3:a:mockjs:mock.js:1.0.0:beta1:*:*:*:node.js:*:*
    cpe:2.3:a:mockjs:mock.js:1.0.0:beta1:*:*:*:node.js:*:*
  • cpe:2.3:a:mockjs:mock.js:1.0.0:beta2:*:*:*:node.js:*:*
    cpe:2.3:a:mockjs:mock.js:1.0.0:beta2:*:*:*:node.js:*:*
  • cpe:2.3:a:mockjs:mock.js:1.0.1:beta1:*:*:*:node.js:*:*
    cpe:2.3:a:mockjs:mock.js:1.0.1:beta1:*:*:*:node.js:*:*
  • cpe:2.3:a:mockjs:mock.js:1.0.1:beta2:*:*:*:node.js:*:*
    cpe:2.3:a:mockjs:mock.js:1.0.1:beta2:*:*:*:node.js:*:*
  • cpe:2.3:a:mockjs:mock.js:1.0.1:beta3:*:*:*:node.js:*:*
    cpe:2.3:a:mockjs:mock.js:1.0.1:beta3:*:*:*:node.js:*:*
  • cpe:2.3:a:mockjs:mock.js:1.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:mockjs:mock.js:1.1.0:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2023-26158: 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-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...
  • CVE-2025-3800 – A vulnerability has been found in WCMS 11 and classified as critical. Affected by this vulnerability is an unknown functionality of the file app/co...
  • CVE-2025-3799 – A vulnerability, which was classified as critical, was found in WCMS 11. Affected is an unknown function of the file app/controllers/AnonymousContr...