Skip to content

TaffyDB can allow access to any data items in the DB

High severity GitHub Reviewed Published Feb 19, 2020 to the GitHub Advisory Database • Updated Jan 30, 2023

Package

npm taffy (npm)

Affected versions

<= 2.6.2

Patched versions

None
npm taffydb (npm)
<= 2.7.3
None

Description

TaffyDB allows attackers to forge adding additional properties into user-input processed by taffy which can allow access to any data items in the DB. Taffy sets an internal index for each data item in its DB. However, it is found that the internal index can be forged by adding additional properties into user-input. If index is found in the query, TaffyDB will ignore other query conditions and directly return the indexed data item. Moreover, the internal index is in an easily-guessable format (e.g., T000002R000001). As such, attackers can use this vulnerability to access any data items in the DB. Note: taffy and its successor package taffydb are not maintained.

References

Published by the National Vulnerability Database Feb 17, 2020
Reviewed Feb 18, 2020
Published to the GitHub Advisory Database Feb 19, 2020
Last updated Jan 30, 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
Unchanged
Confidentiality
High
Integrity
None
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:U/C:H/I:N/A:N

EPSS score

0.718%
(80th percentile)

Weaknesses

CVE ID

CVE-2019-10790

GHSA ID

GHSA-mxhp-79qh-mcx6

Source code

Credits

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