Skip to content

Prototype Pollution in Dynamoose

High severity GitHub Reviewed Published Feb 6, 2021 in dynamoose/dynamoose • Updated Feb 1, 2023

Package

npm dynamoose (npm)

Affected versions

>= 2.0.0, < 2.7.0

Patched versions

2.7.0

Description

Impact

In Dynamoose versions 2.0.0-2.6.0 there was a prototype pollution vulnerability in the internal utility method lib/utils/object/set.ts. This method is used throughout the codebase for various operations throughout Dynamoose.

We have not seen any evidence of this vulnerability being exploited.

We do not believe this issue impacts v1.x.x since this method was added as part of the v2 rewrite. This vulnerability also impacts v2.x.x beta/alpha versions.

Patches

v2.7.0 includes a patch for this vulnerability.

Workarounds

We are unaware of any workarounds to patch this vulnerability other than upgrading to v2.7.0 or greater.

References

  • Patch commit hash: 324c62b4709204955931a187362f8999805b1d8e

For more information

If you have any questions or comments about this advisory:

Credit

  • GitHub CodeQL Code Scanning

References

@fishcharlie fishcharlie published to dynamoose/dynamoose Feb 6, 2021
Reviewed Feb 8, 2021
Published to the GitHub Advisory Database Feb 8, 2021
Published by the National Vulnerability Database Feb 8, 2021
Last updated Feb 1, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

EPSS score

0.436%
(75th percentile)

Weaknesses

CVE ID

CVE-2021-21304

GHSA ID

GHSA-rrqm-p222-8ph2

Source code

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