{"answers":{"affected":"4 open source packages ship an affected version, including taffy and taffydb. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10790 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2019-10790 is a high-severity missing authorization vulnerability in taffy npm module, published on 17 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10790 and fix it if it is affected.\n\nWhat it is: CVE-2019-10790 is a high-severity missing authorization vulnerability in taffy npm module, published on 17 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-10790 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- taffy (npm): affected all versions up to 2.6.2; no fix listed\n- taffy (npm): affected all versions up to 2.6.2; no fix listed\n- taffydb (npm): affected all versions up to 2.7.3; no fix listed\n- taffydb (npm): affected all versions up to 2.7.3; no fix listed\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-10790/ (Markdown: https://insights.sbomify.com/CVE-2019-10790/index.md)","id":"CVE-2019-10790","markdown":"https://insights.sbomify.com/CVE-2019-10790/index.md","name":"CVE-2019-10790","record":{"aliases":["GHSA-mxhp-79qh-mcx6","MINI-6939-89v5-32h2"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript database library","requires_auth":"none","summary":"Attackers can forge internal indices to bypass query conditions and access any data items in the taffydb database.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"taffy","vendor":"taffydb"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"}],"description":"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"TaffyDB can allow access to any data items in the DB","id":"CVE-2019-10790","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"missing_authorization","year":"2019"},"n_packages":4,"n_references":2,"next":{"headline":"promise-probe OS command injection vulnerability","id":"CVE-2019-10791"},"packages":[{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2.6.2"],"package":"taffy","purl":null,"source":"GHSA-mxhp-79qh-mcx6"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2.6.2"],"package":"taffy","purl":"pkg:npm/taffy","source":"GHSA-mxhp-79qh-mcx6"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2.7.3"],"package":"taffydb","purl":null,"source":"GHSA-mxhp-79qh-mcx6"},{"ecosystem":"npm","fixed":[],"introduced":["0"],"last_affected":["2.7.3"],"package":"taffydb","purl":"pkg:npm/taffydb","source":"GHSA-mxhp-79qh-mcx6"}],"prev":{"headline":"OS Command Injection in curling","id":"CVE-2019-10789"},"products":["taffy npm module"],"published":"2020-02-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can forge internal indices to bypass query conditions and access any data items in the taffydb database.","url":"https://insights.sbomify.com/CVE-2019-10790/"}