{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2009-2943 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2009-2943 is a high-severity SQL injection vulnerability in n/a, published on 22 Oct 2009. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2009-2943 and fix it if it is affected.\n\nWhat it is: CVE-2009-2943 is a high-severity SQL injection vulnerability in n/a, published on 22 Oct 2009. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2009-2943 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-2009-2943/ (Markdown: https://insights.sbomify.com/CVE-2009-2943/index.md)","id":"CVE-2009-2943","markdown":"https://insights.sbomify.com/CVE-2009-2943/index.md","name":"CVE-2009-2943","record":{"aliases":["DEBIAN-CVE-2009-2943","DSA-1909-1","GHSA-vvfr-p62m-9frc"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"PostgreSQL OCaml bindings","requires_auth":"low_privilege","summary":"Remote attackers can exploit improper string escaping in PostgreSQL OCaml bindings to perform SQL injection attacks.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"postgresql-ocaml","vendor":"ocaml"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"The postgresql-ocaml bindings 1.5.4, 1.7.0, and 1.12.1 for PostgreSQL libpq do not properly support the PQescapeStringConn function, which might allow remote attackers to leverage escaping issues involving multibyte character encodings.","ecosystems":[],"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 n/a","id":"CVE-2009-2943","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2009"},"n_packages":0,"n_references":3,"next":{"headline":"Path traversal in n/a","id":"CVE-2009-2944"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2009-2942"},"products":["n/a"],"published":"2009-10-22","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Remote attackers can exploit improper string escaping in PostgreSQL OCaml bindings to perform SQL injection attacks.","url":"https://insights.sbomify.com/CVE-2009-2943/"}