Lucene search

K
osvGoogleOSV:DSA-1087-1
HistoryJun 03, 2006 - 12:00 a.m.

postgresql - programming error

2006-06-0300:00:00
Google
osv.dev
15

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.024 Low

EPSS

Percentile

88.3%

Several encoding problems have been discovered in PostgreSQL, a
popular SQL database. The Common Vulnerabilities and Exposures
project identifies the following problems:

  • CVE-2006-2313
    Akio Ishida and Yasuo Ohgaki discovered a weakness in the handling
    of invalidly-encoded multibyte text data which could allow an
    attacker to inject arbitrary SQL commands.
  • CVE-2006-2314
    A similar problem exists in client-side encodings (such as SJIS,
    BIG5, GBK, GB18030, and UHC) which contain valid multibyte
    characters that end with the backslash character. An attacker
    could supply a specially crafted byte sequence that is able to
    inject arbitrary SQL commands.

This issue does not affect you if you only use single-byte (like
SQL_ASCII or the ISO-8859-X family) or unaffected multibyte (like
UTF-8) encodings.

psycopg and python-pgsql use the old encoding for binary data and
may have to be updated.

The old stable distribution (woody) is affected by these problems but
we’re unable to correct the package.

For the stable distribution (sarge) these problems have been fixed in
version 7.4.7-6sarge2.

For the unstable distribution (sid) these problems have been fixed in
version 7.4.13-1.

We recommend that you upgrade your postgresql packages.

CPENameOperatorVersion
postgresqleq7.4.7-6sarge1

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.024 Low

EPSS

Percentile

88.3%