flattenizer vulnerable to prototype pollution
Critical severity
GitHub Reviewed
Published
May 24, 2022
to the GitHub Advisory Database
•
Updated Apr 10, 2024
Description
Published by the National Vulnerability Database
Dec 29, 2020
Published to the GitHub Advisory Database
May 24, 2022
Reviewed
Apr 1, 2024
Last updated
Apr 10, 2024
Overview
Prototype pollution vulnerability in ‘flattenizer’ versions 0.0.5 through 1.0.5 allows an attacker to cause a denial of service and may lead to remote code execution.
Details
The NPM module 'flattenizer' can be abused by Prototype Pollution vulnerability since the function 'unflatten()' 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
There is no validation before assigning the property to check whether the assigned argument is the Object's own property or not, the property
polluted
will be directly be assigned thereby polluting the Object prototype. Later in the code, if there is a check to validatepolluted
the valued would be substituted as "true" as it had been polluted.References