{"answers":{"affected":"2 open source packages ship an affected version, including waterline-sequel. It affects 1 product.","exploited":"There is no known exploitation of CVE-2016-10551 in the wild and no public exploit code.","fix":"Upgrade waterline-sequel to 0.5.1 or later.","what":"CVE-2016-10551 is a critical SQL injection vulnerability in HackerOne waterline-sequel 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-10551 and fix it if it is affected.\n\nWhat it is: CVE-2016-10551 is a critical SQL injection vulnerability in HackerOne waterline-sequel 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-10551 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- waterline-sequel (npm): affected all versions; fixed in 0.5.1\n- waterline-sequel (npm): affected all versions; fixed in 0.5.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-2016-10551/ (Markdown: https://insights.sbomify.com/CVE-2016-10551/index.md)","id":"CVE-2016-10551","markdown":"https://insights.sbomify.com/CVE-2016-10551/index.md","name":"CVE-2016-10551","record":{"aliases":["GHSA-cgpp-wm2h-6hqx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js SQL library","requires_auth":"none","summary":"Attackers can inject SQL via user input in waterline-sequel, gaining full database access. Developers using this Node.js module should upgrade.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"hackerone","cpe":[{"product":"waterline-sequel","vendor":"balderdash"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"waterline-sequel is a module that helps generate SQL statements for Waterline apps Any user input that goes into Waterline's `like`, `contains`, `startsWith`, or `endsWith` will end up in waterline-sequel with the potential for malicious code. A malicious user can input their own SQL statements in waterline-sequel 0.50 that will get executed and have full access to the database.","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 waterline-sequel","id":"CVE-2016-10551","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":"Resources Downloaded over Insecure Protocol in igniteui","id":"CVE-2016-10552"},"packages":[{"ecosystem":"npm","fixed":["0.5.1"],"introduced":["0"],"last_affected":[],"package":"waterline-sequel","purl":null,"source":"GHSA-cgpp-wm2h-6hqx"},{"ecosystem":"npm","fixed":["0.5.1"],"introduced":["0"],"last_affected":[],"package":"waterline-sequel","purl":"pkg:npm/waterline-sequel","source":"GHSA-cgpp-wm2h-6hqx"}],"prev":{"headline":"SQL Injection in sequelize","id":"CVE-2016-10550"},"products":["waterline-sequel node module"],"published":"2018-05-29","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":["HackerOne"]},"summary":"Attackers can inject SQL via user input in waterline-sequel, gaining full database access. Developers using this Node.js module should upgrade.","url":"https://insights.sbomify.com/CVE-2016-10551/"}