{"answers":{"affected":"2 open source packages ship an affected version, including mysql2. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-21509 exists.","fix":"Upgrade mysql2 to 3.9.4 or later.","what":"CVE-2024-21509 is a medium-severity code injection vulnerability in mysql2, published on 10 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-21509 and fix it if it is affected.\n\nWhat it is: CVE-2024-21509 is a medium-severity code injection vulnerability in mysql2, published on 10 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-21509 exists.\n\nAffected packages and fixed versions:\n- mysql2 (npm): affected all versions; fixed in 3.9.4\n- mysql2 (npm): affected all versions; fixed in 3.9.4\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-2024-21509/ (Markdown: https://insights.sbomify.com/CVE-2024-21509/index.md)","id":"CVE-2024-21509","markdown":"https://insights.sbomify.com/CVE-2024-21509/index.md","name":"CVE-2024-21509","record":{"aliases":["CLSA-2026-1786373168","GHSA-49j4-86m8-q2jw","ROOT-APP-NPM-CVE-2024-21509"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"MySQL client library","requires_auth":"none","summary":"Prototype poisoning in mysql2 allows attackers to execute arbitrary code via insecure object creation and input sanitization flaws.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"snyk","cpe":[{"product":"mysql2","vendor":"sidorares"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L/E:P","version":"3.1"},"cwes":[{"id":"CWE-1321","name":"Improperly Controlled Modification of Object Prototype Attributes"}],"description":"Versions of the package mysql2 before 3.9.4 are vulnerable to Prototype Poisoning due to insecure results object creation and improper user input sanitization passed through parserFn in text_parser.js and binary_parser.js.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"mysql2 vulnerable to Prototype Poisoning","id":"CVE-2024-21509","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"code_injection","year":"2024"},"n_packages":2,"n_references":6,"next":{"headline":"Sinatra vulnerable to Reliance on Untrusted Inputs in a Security Decision","id":"CVE-2024-21510"},"packages":[{"ecosystem":"npm","fixed":["3.9.4"],"introduced":["0"],"last_affected":[],"package":"mysql2","purl":null,"source":"GHSA-49j4-86m8-q2jw"},{"ecosystem":"npm","fixed":["3.9.4"],"introduced":["0"],"last_affected":[],"package":"mysql2","purl":"pkg:npm/mysql2","source":"GHSA-49j4-86m8-q2jw"}],"prev":{"headline":"mysql2 Remote Code Execution (RCE) via the readCodeFor function","id":"CVE-2024-21508"},"products":["mysql2"],"published":"2024-04-10","related":[{"cvss_score":6.5,"headline":"mysql2 cache poisoning vulnerability","id":"CVE-2024-21507","kev_date_added":null,"published":"2024-04-10"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-22","vendors":["n/a"]},"summary":"Prototype poisoning in mysql2 allows attackers to execute arbitrary code via insecure object creation and input sanitization flaws.","url":"https://insights.sbomify.com/CVE-2024-21509/"}