Advisory

GHSA-xv6x-43gq-4hfj

Also known as: CVE-2009-2940, PYSEC-2009-18

Summary

PyGreSQL Might Be Vulnerable to Encoding-Based SQL Injection

Details

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)

Severity

High Basis: The source's own band: HIGH

Dates

Published
2022-05-02 03:40 UTC
Modified
2026-06-08 19:15 UTC

Affected packages and fixes

pygresql

PyPI · All systems

Affected

  • introduced 0, last affected 3.8.1 (ecosystem)

Fixed versions

None listed

Fix

No fixed version is listed.

pygresql

PyPI · All systems

Affected

  • introduced 4.0, fixed 4.1 (ecosystem)

Fixed versions

4.1

Fix

  • Fixed version 4.1
    pip install --upgrade pygresql==4.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences