Skip to content

keyget vulnerable to prototype pollution

Critical severity GitHub Reviewed Published May 24, 2022 to the GitHub Advisory Database • Updated Oct 19, 2023

Package

npm keyget (npm)

Affected versions

>= 1.0.0, <= 2.2.0

Patched versions

2.3.0

Description

Overview

Prototype pollution vulnerability in 'keyget' versions 1.0.0 through 2.2.0 allows attacker to cause a denial of service and may lead to remote code execution.

Details

The npm module 'keyget' can be abused by Prototype Pollution vulnerability since the function 'setByPath()' did not check for the type of object before assigning value to the property. Due to this flaw an attacker could create a non-existent property or able to manipulate the property which leads to Denial of Service or potentially Remote code execution.

PoC Details

The setByPath() function accepts three arguments target, path, value. Due to the absence of validation, at values passed into path, value an attacker can supply a malicious value by adjusting the path value to include the __proto__ property. Since there is no validation before assigning property to check whether the assigned path is the Object's own property or not, the property polluted will be directly be assigned to the empty obj({}) thereby polluting the Object prototype. Later in the code, if there is a check to validate polluted the value would be substituted as "true" as it had been polluted.

PoC Code

var keyget = require("keyget")
 keyget.set({}, '__proto__.polluted', 'true');
 console.log(polluted); 

References

Published by the National Vulnerability Database Dec 2, 2020
Published to the GitHub Advisory Database May 24, 2022
Reviewed Oct 19, 2023
Last updated Oct 19, 2023

Severity

Critical
9.8
/ 10

CVSS base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Weaknesses

CVE ID

CVE-2020-28272

GHSA ID

GHSA-8mp8-28xh-r486

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.