{"answers":{"affected":"4 open source packages ship an affected version, including dexie. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-21189 in the wild and no public exploit code.","fix":"Upgrade dexie to a fixed version for your release line: 3.2.2 or 4.0.0-alpha.3.","what":"CVE-2022-21189 is a high-severity vulnerability in dexie, published on 1 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-21189 and fix it if it is affected.\n\nWhat it is: CVE-2022-21189 is a high-severity vulnerability in dexie, published on 1 May 2022. 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-2022-21189 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- dexie (npm): affected all versions; fixed in 3.2.2\n- dexie (npm): affected all versions; fixed in 3.2.2\n- dexie (npm): affected from 4.0.0-alpha.1; fixed in 4.0.0-alpha.3\n- dexie (npm): affected from 4.0.0-alpha.1; fixed in 4.0.0-alpha.3\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-2022-21189/ (Markdown: https://insights.sbomify.com/CVE-2022-21189/index.md)","id":"CVE-2022-21189","markdown":"https://insights.sbomify.com/CVE-2022-21189/index.md","name":"CVE-2022-21189","record":{"aliases":["GHSA-3xgx-r9j4-qw9w"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"JavaScript database library","requires_auth":"none","summary":"Attackers can pollute Object.prototype via untrusted input in Dexie, potentially leading to code execution or security bypasses.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"dexie","vendor":"dexie"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L/E:P","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"The package dexie before 3.2.2, from 4.0.0-alpha.1 and before 4.0.0-alpha.3 are vulnerable to Prototype Pollution in the Dexie.setByKeyPath(obj, keyPath, value) function which does not properly check the keys being set (like __proto__ or constructor). This can allow an attacker to add/modify properties of the Object.prototype leading to prototype pollution vulnerability. **Note:** This vulnerability can occur in multiple ways, for example when modifying a collection with untrusted user input.","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":"Prototype Pollution","id":"CVE-2022-21189","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"other","year":"2022"},"n_packages":4,"n_references":4,"next":{"headline":"Prototype Pollution","id":"CVE-2022-21190"},"packages":[{"ecosystem":"npm","fixed":["3.2.2"],"introduced":["0"],"last_affected":[],"package":"dexie","purl":null,"source":"GHSA-3xgx-r9j4-qw9w"},{"ecosystem":"npm","fixed":["3.2.2"],"introduced":["0"],"last_affected":[],"package":"dexie","purl":"pkg:npm/dexie","source":"GHSA-3xgx-r9j4-qw9w"},{"ecosystem":"npm","fixed":["4.0.0-alpha.3"],"introduced":["4.0.0-alpha.1"],"last_affected":[],"package":"dexie","purl":null,"source":"GHSA-3xgx-r9j4-qw9w"},{"ecosystem":"npm","fixed":["4.0.0-alpha.3"],"introduced":["4.0.0-alpha.1"],"last_affected":[],"package":"dexie","purl":"pkg:npm/dexie","source":"GHSA-3xgx-r9j4-qw9w"}],"prev":{"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority because it is Unused","id":"CVE-2022-21188"},"products":["dexie"],"published":"2022-05-01","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-09-16","vendors":["n/a"]},"summary":"Attackers can pollute Object.prototype via untrusted input in Dexie, potentially leading to code execution or security bypasses.","url":"https://insights.sbomify.com/CVE-2022-21189/"}