CVE-2021-21368 Vulnerability Analysis & Exploit Details

CVE-2021-21368
Vulnerability Scoring

6.7
/10
High Risk

If left unpatched, CVE-2021-21368 could lead to major system disruptions or data loss.

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: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: Required
    User interaction is necessary for successful exploitation.

CVE-2021-21368 Details

Status: Modified

Last updated: 🕠 21 Nov 2024, 05:48 UTC
Originally published on: 🕔 12 Mar 2021, 17:15 UTC

Time between publication and last update: 1349 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

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

CVE-2021-21368 Vulnerability Summary

CVE-2021-21368: msgpack5 is a msgpack v5 implementation for node.js and the browser. In msgpack5 before versions 3.6.1, 4.5.1, and 5.2.1 there is a "Prototype Poisoning" vulnerability. When msgpack5 decodes a map containing a key "__proto__", it assigns the decoded value to __proto__. Object.prototype.__proto__ is an accessor property for the receiver's prototype. If the value corresponding to the key __proto__ decodes to an object or null, msgpack5 sets the decoded object's prototype to that value. An attacker who can submit crafted MessagePack data to a service can use this to produce values that appear to be of other types; may have unexpected prototype properties and methods (for example length, numeric properties, and push et al if __proto__'s value decodes to an Array); and/or may throw unexpected exceptions when used (for example if the __proto__ value decodes to a Map or Date). Other unexpected behavior might be produced for other types. There is no effect on the global prototype. This "prototype poisoning" is sort of a very limited inversion of a prototype pollution attack. Only the decoded value's prototype is affected, and it can only be set to msgpack5 values (though if the victim makes use of custom codecs, anything could be a msgpack5 value). We have not found a way to escalate this to true prototype pollution (absent other bugs in the consumer's code). This has been fixed in msgpack5 version 3.6.1, 4.5.1, and 5.2.1. See the referenced GitHub Security Advisory for an example and more details.

Assessing the Risk of CVE-2021-21368

Access Complexity Graph

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

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

  • Confidentiality: Low
    CVE-2021-21368 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: High
    CVE-2021-21368 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
  • Availability: High
    CVE-2021-21368 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: 1.269% (probability of exploit)

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

CVE-2021-21368 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:msgpack5_project:msgpack5:-:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:-:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:1.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:1.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:1.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:1.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:1.3.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:1.3.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:1.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:1.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:1.6.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:1.6.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:2.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:2.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:2.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:2.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:2.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:2.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:2.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:2.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:2.3.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:2.3.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:3.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:3.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:3.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:3.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:3.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:3.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:3.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:3.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:3.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:3.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:3.4.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:3.4.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:3.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:3.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:3.6.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:3.6.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:4.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:4.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:4.0.1:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:4.0.1:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:4.0.2:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:4.0.2:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:4.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:4.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:4.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:4.2.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:4.3.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:4.3.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:4.4.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:4.4.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:4.5.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:4.5.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:5.0.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:5.0.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:5.1.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:5.1.0:*:*:*:*:node.js:*:*
  • cpe:2.3:a:msgpack5_project:msgpack5:5.2.0:*:*:*:*:node.js:*:*
    cpe:2.3:a:msgpack5_project:msgpack5:5.2.0:*:*:*:*:node.js:*:*

Protect Your Infrastructure against CVE-2021-21368: 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-31203 – An integer overflow was addressed with improved input validation. This issue is fixed in macOS Sequoia 15.4, tvOS 18.4, iPadOS 17.7.6, macOS Sonoma...
  • CVE-2025-31202 – A null pointer dereference was addressed with improved input validation. This issue is fixed in iOS 18.4 and iPadOS 18.4, macOS Sequoia 15.4, tvOS ...
  • CVE-2025-31197 – The issue was addressed with improved checks. This issue is fixed in macOS Sequoia 15.4, tvOS 18.4, macOS Ventura 13.7.5, iPadOS 17.7.6, macOS Sono...
  • CVE-2025-30445 – A type confusion issue was addressed with improved checks. This issue is fixed in macOS Sequoia 15.4, tvOS 18.4, macOS Ventura 13.7.5, iPadOS 17.7....
  • CVE-2025-24271 – An access issue was addressed with improved access restrictions. This issue is fixed in macOS Sequoia 15.4, tvOS 18.4, macOS Ventura 13.7.5, iPadOS...