{"answers":{"affected":"4 open source packages ship an affected version, including @sequelize/core and sequelize. It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-22579 in the wild and no public exploit code.","fix":"Upgrade @sequelize/core to 7.0.0-alpha.20 or later.","what":"CVE-2023-22579 is a critical SQL injection vulnerability in Feathers-Sequalize Sequelize.js, published on 16 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-22579 and fix it if it is affected.\n\nWhat it is: CVE-2023-22579 is a critical SQL injection vulnerability in Feathers-Sequalize Sequelize.js, published on 16 Feb 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-22579 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- @sequelize/core (npm): affected all versions; fixed in 7.0.0-alpha.20\n- @sequelize/core (npm): affected all versions; fixed in 7.0.0-alpha.20\n- sequelize (npm): affected all versions; fixed in 6.28.1\n- sequelize (npm): affected all versions; fixed in 6.28.1\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-2023-22579/ (Markdown: https://insights.sbomify.com/CVE-2023-22579/index.md)","id":"CVE-2023-22579","markdown":"https://insights.sbomify.com/CVE-2023-22579/index.md","name":"CVE-2023-22579","record":{"aliases":["GHSA-vqfx-gj96-3w95"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Sequelize.js library","requires_auth":"low_privilege","summary":"Attackers can perform SQL injection via improper parameter filtering in the Sequelize.js library, potentially accessing or modifying database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"DIVD","cpe":[{"product":"sequelize","vendor":"sequelizejs"}],"cvss":{"score":9.9,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-843","name":"Access of Resource Using Incompatible Type"}],"description":"Due to improper parameter filtering in the sequalize js library, can a attacker peform injection.","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":"Sequalize - Unsafe fall-through in getWhereConditions","id":"CVE-2023-22579","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"sql_injection","year":"2023"},"n_packages":4,"n_references":2,"next":{"headline":"Sequalize - Bad query filtering leading to SQL errors","id":"CVE-2023-22580"},"packages":[{"ecosystem":"npm","fixed":["7.0.0-alpha.20"],"introduced":["0"],"last_affected":[],"package":"@sequelize/core","purl":null,"source":"GHSA-vqfx-gj96-3w95"},{"ecosystem":"npm","fixed":["7.0.0-alpha.20"],"introduced":["0"],"last_affected":[],"package":"@sequelize/core","purl":"pkg:npm/%40sequelize/core","source":"GHSA-vqfx-gj96-3w95"},{"ecosystem":"npm","fixed":["6.28.1"],"introduced":["0"],"last_affected":[],"package":"sequelize","purl":null,"source":"GHSA-vqfx-gj96-3w95"},{"ecosystem":"npm","fixed":["6.28.1"],"introduced":["0"],"last_affected":[],"package":"sequelize","purl":"pkg:npm/sequelize","source":"GHSA-vqfx-gj96-3w95"}],"prev":{"headline":"Sequalize - Default support for “raw attributes” when using parentheses","id":"CVE-2023-22578"},"products":["Sequelize.js"],"published":"2023-02-16","related":[{"cvss_score":10,"headline":"SQL Injection via replacements in sequelize","id":"CVE-2023-25813","kev_date_added":null,"published":"2023-02-22"},{"cvss_score":10,"headline":"Sequalize - Default support for “raw attributes” when using parentheses","id":"CVE-2023-22578","kev_date_added":null,"published":"2023-02-16"},{"cvss_score":9.8,"headline":"SQL Injection in sequelize","id":"CVE-2019-10749","kev_date_added":null,"published":"2019-10-29"},{"cvss_score":9.8,"headline":"SQL Injection in sequelize","id":"CVE-2019-10748","kev_date_added":null,"published":"2019-10-28"},{"cvss_score":9.8,"headline":"SQL Injection in sequelize","id":"CVE-2019-10752","kev_date_added":null,"published":"2019-10-17"},{"cvss_score":9.8,"headline":"SQL Injection in sequelize","id":"CVE-2016-10550","kev_date_added":null,"published":"2018-05-31"}],"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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-01","vendors":["Feathers-Sequalize"]},"summary":"Attackers can perform SQL injection via improper parameter filtering in the Sequelize.js library, potentially accessing or modifying database contents.","url":"https://insights.sbomify.com/CVE-2023-22579/"}