PyGreSQL 3.8 did not use PostgreSQL’s safe string
and bytea
functions in its own escaping functions. As a result, applications written to use PyGreSQL’s escaping functions are vulnerable to SQL injections when processing certain multi-byte character sequences. Because the safe functions require a database connection, to maintain backwards compatibility, pg.escape_string()
and pg.escape_bytea()
are still available, but applications will have to be adjusted to use the new pyobj.escape_string()
and pyobj.escape_bytea()
functions. For example, code containing:
import pg
connection = pg.connect(...)
escaped = pg.escape_string(untrusted_input)
should be adjusted to use:
import pg
connection = pg.connect(...)
escaped = connection.escape_string(untrusted_input)
{ "nvd_published_at": "2009-10-22T16:30:00Z", "cwe_ids": [ "CWE-89" ], "severity": "HIGH", "github_reviewed": true, "github_reviewed_at": "2024-02-08T21:31:52Z" }