Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

taffy npm module · Vulnerability

cve-program · severity unknowneuvd · severity unknownCVSS 3.1 · [email protected] · Primary 7.5 HIGHCVSS 2.0 · [email protected] · Primary 5.0 MEDIUMCVSS_V3 Publisher rating HIGHCheck source for fixed versionsKEV status unknown

cve-program · CVE-2019-10790

Published

taffydb npm module, vulnerable in all versions up to and including 2.7.3, 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.

Read the publisher's advisory

euvd · EUVD-2020-0307

Published

taffydb npm module, vulnerable in all versions up to and including 2.7.3, 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.

Read the publisher's advisory

nvd · CVE-2019-10790

Published

taffydb npm module, vulnerable in all versions up to and including 2.7.3, 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.

Read the publisher's advisory

osv · GHSA-mxhp-79qh-mcx6

Published

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.

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2019-10790

Published

taffy npm module

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "n/a",
                    "product": "taffy npm module",
                    "versions": [
                        {
                            "version": "All versions including 2.6.2",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2020-0307

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Feb 17, 2020, 12:00:00 AM

dateUpdated: Aug 4, 2024, 10:32:01 PM

5 related source bulletins · separate from aliases

RHSA-2026:2737: Red Hat Security Advisory: Red Hat Ceph Storage

CVE-2019-10790 · CVE-2021-23358 · CVE-2022-34749 · CVE-2024-31884 · CVE-2024-51744 · CVE-2024-55565 · CVE-2025-6176 · CVE-2025-7783 · CVE-2025-12816 · CVE-2025-14104 · CVE-2025-26791 · CVE-2025-47907 · CVE-2025-47913 · CVE-2025-58183 · CVE-2025-66031 · CVE-2025-66418 · CVE-2025-66471 · CVE-2025-68429

RHSA-2026:83548: Red Hat Security Advisory: Red Hat Ceph Storage

CVE-2019-10790 · CVE-2023-25153 · CVE-2023-28155 · CVE-2023-46159 · CVE-2024-5206 · CVE-2024-11831 · CVE-2024-37890 · CVE-2024-47866 · CVE-2025-7783 · CVE-2025-30156 · CVE-2025-47914 · CVE-2025-50181 · CVE-2025-50182 · CVE-2025-58181 · CVE-2025-59436 · CVE-2025-64718 · CVE-2025-64756 · CVE-2026-50152

RHSA-2026:62115: Red Hat Security Advisory: Red Hat Ceph Storage

CVE-2019-10790 · CVE-2023-25153 · CVE-2023-28155 · CVE-2024-11831 · CVE-2025-50181 · CVE-2025-50182 · CVE-2025-59436 · CVE-2025-66418 · CVE-2026-24049

RHSA-2026:2711: Red Hat Security Advisory: Red Hat Ceph Storage 8.1 security and bug fix update

CVE-2019-10790 · CVE-2022-34749 · CVE-2024-31884 · CVE-2025-58183

RHSA-2026:3406: Red Hat Security Advisory: New container image: rhceph-9.0

CVE-2021-23358 · CVE-2024-45310 · CVE-2024-51744 · CVE-2024-55565 · CVE-2025-6176 · CVE-2025-7783 · CVE-2025-14104 · CVE-2025-22868 · CVE-2025-26791 · CVE-2025-50181 · CVE-2025-50182 · CVE-2025-66418 · CVE-2025-66471 · CVE-2026-21441

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2019-10790

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-668

Original publisher date fields

published: 2020-02-17T20:15:10.943

lastModified: 2026-06-17T02:11:40.713

1 source CPE criteria · context only
  • cpe:2.3:a:taffydb:taffy:*:*:*:*:*:node.js:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-mxhp-79qh-mcx6

Published

taffy

npm

SEMVER · introduced 0 → last_affected 2.6.2

taffydb

npm

SEMVER · introduced 0 → last_affected 2.7.3

Original source record · Cite this exact observation · Complete original publisher JSON

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 19 Nov 05:53 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current