{"answers":{"affected":"2 open source packages ship an affected version, including sequelize. It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-10556 in the wild and no public exploit code.","fix":"Upgrade sequelize to 3.20.0 or later.","what":"CVE-2016-10556 is a high-severity SQL injection vulnerability in HackerOne sequelize node module, published on 29 May 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2016-10556 and fix it if it is affected.\n\nWhat it is: CVE-2016-10556 is a high-severity SQL injection vulnerability in HackerOne sequelize node module, published on 29 May 2018. 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-2016-10556 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- sequelize (npm): affected all versions; fixed in 3.20.0\n- sequelize (npm): affected all versions; fixed in 3.20.0\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-2016-10556/ (Markdown: https://insights.sbomify.com/CVE-2016-10556/index.md)","id":"CVE-2016-10556","markdown":"https://insights.sbomify.com/CVE-2016-10556/index.md","name":"CVE-2016-10556","record":{"aliases":["GHSA-9c2p-jw8p-f84v"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js ORM library","requires_auth":"none","summary":"Attackers can execute arbitrary SQL commands via improper array escaping in Sequelize when using Postgres, SQLite, or MSSQL.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"sequelize","vendor":"sequelizejs"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"sequelize is an Object-relational mapping, or a middleman to convert things from Postgres, MySQL, MariaDB, SQLite and Microsoft SQL Server into usable data for NodeJS In Postgres, SQLite, and Microsoft SQL Server there is an issue where arrays are treated as strings and improperly escaped. This causes potential SQL injection in sequelize 3.19.3 and earlier, where a malicious user could put `[\"test\", \"'); DELETE TestTable WHERE Id = 1 --')\"]` inside of ``` database.query('SELECT * FROM TestTable WHERE Name IN (:names)', { replacements: { names: directCopyOfUserInput } }); ``` and cause the SQL statement to become `SELECT Id FROM Table WHERE Name IN ('test', '\\'); DELETE TestTable WHERE Id = 1 --')`. In Postgres, MSSQL, and SQLite, the backslash has no special meaning. This causes the the statement to delete whichever Id has a value of 1 in the TestTable table.","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":"SQL Injection in sequelize","id":"CVE-2016-10556","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"sql_injection","year":"2016"},"n_packages":2,"n_references":2,"next":{"headline":"appium-chromedriver downloads Resources over HTTP","id":"CVE-2016-10557"},"packages":[{"ecosystem":"npm","fixed":["3.20.0"],"introduced":["0"],"last_affected":[],"package":"sequelize","purl":null,"source":"GHSA-9c2p-jw8p-f84v"},{"ecosystem":"npm","fixed":["3.20.0"],"introduced":["0"],"last_affected":[],"package":"sequelize","purl":"pkg:npm/sequelize","source":"GHSA-9c2p-jw8p-f84v"}],"prev":{"headline":"Forgeable Public/Private Tokens in jwt-simple","id":"CVE-2016-10555"},"products":["sequelize node module"],"published":"2018-05-29","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.9,"headline":"Sequalize - Unsafe fall-through in getWhereConditions","id":"CVE-2023-22579","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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["HackerOne"]},"summary":"Attackers can execute arbitrary SQL commands via improper array escaping in Sequelize when using Postgres, SQLite, or MSSQL.","url":"https://insights.sbomify.com/CVE-2016-10556/"}