defaults-deep up to 0.2.4 on npm Prototype injection

Summaryinfo

A vulnerability classified as critical has been found in defaults-deep up to 0.2.4 on npm. Affected by this issue is some unknown functionality of the component Prototype Handler. Performing a manipulation results in injection. This vulnerability is known as CVE-2018-16486. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability, which was classified as critical, was found in defaults-deep up to 0.2.4 on npm. This affects some unknown processing of the component Prototype Handler. The manipulation with an unknown input leads to a injection vulnerability. CWE is classifying the issue as CWE-74. The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

A prototype pollution vulnerability was found in defaults-deep <=0.2.4 that would allow a malicious user to inject properties onto Object.prototype.

The bug was discovered 09/28/2018. The weakness was published 02/01/2019 (Website). It is possible to read the advisory at hackerone.com. This vulnerability is uniquely identified as CVE-2018-16486 since 09/04/2018. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1055 according to MITRE ATT&CK.

The vulnerability was handled as a non-public zero-day exploit for at least 126 days. During that time the estimated underground price was around $0-$5k.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• NPM Package

Name

• defaults-deep

Version

• 0.2.0
• 0.2.1
• 0.2.2
• 0.2.3
• 0.2.4

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion