It was discovered that postgresql-ocaml, OCaml bindings to PostgreSQL's libpq, was missing a function to call PQescapeStringConn(). This is needed, because PQescapeStringConn() honours the charset of the connection and prevents insufficient escaping, when certain multibyte character encodings are used. The added function is called escape_string_conn() and takes the established database connection as a first argument. The old escape_string() was kept for backwards compatibility. Developers using these bindings are encouraged to adjust their code to use the new function. Reproducible: Didn't try
CVE-2009-2943 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2009-2943): 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.
2009-09-18: Fixed serious bug in new escape_string method. PLEASE UPGRADE!!! 2009-09-08: API-change: deleted "escape_string" function. There is now a method "escape_string" in the connection class, which is not deprecated and hence safer. ??? I see no mention of latest version in those cve & bug reports.
Time to revisit this. None of the versions available in the tree are listed in the CVE. 1.7.0 was removed three years ago. (A year and half before this bug was reported.) 1.12.1 was removed a year ago. 1.5.4 never was in the tree. According to the ChangeLog anyway.
Vulnerable version removed 09 Apr 2010. Closing noglsa.