6.3 Medium
AI Score
Confidence
Low
7.5 High
CVSS2
Access Vector
NETWORK
Access Complexity
LOW
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
PARTIAL
AV:N/AC:L/Au:N/C:P/I:P/A:P
0.011 Low
EPSS
Percentile
83.9%
Steffen Joeris discovered that 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)
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
Ubuntu | 8.10 | noarch | python-pygresql | < 1:3.8.1-3ubuntu0.1 | UNKNOWN |
Ubuntu | 8.10 | noarch | python-pygresql-dbg | < 1:3.8.1-3ubuntu0.1 | UNKNOWN |
Ubuntu | 8.04 | noarch | python-pygresql | < 1:3.8.1-2ubuntu0.1 | UNKNOWN |
Ubuntu | 8.04 | noarch | python-pygresql-dbg | < 1:3.8.1-2ubuntu0.1 | UNKNOWN |