[ GLSA 201110-22 ] PostgreSQL: Multiple vulnerabilities

[GLSA]

Gentoo Linux Security Advisory

Title: PostgreSQL: Multiple vulnerabilities (GLSA 201110-22)
Severity: normal
Exploitable: remote
Date: October 25, 2011
Updated: March 05, 2012
Bug(s): #261223, #284274, #297383, #308063, #313335, #320967, #339935, #353387, #384539
ID: 201110-22

Synopsis

Multiple vulnerabilities in the PostgreSQL server and client allow
remote attacker to conduct several attacks, including the execution of
arbitrary code and Denial of Service.


Background

PostgreSQL is an open source object-relational database management
system.


Affected Packages

Package: dev-db/postgresql
Vulnerable: <= 9
Architectures: All supported architectures

Package: dev-db/postgresql-server
Vulnerable: < 9.0.5
Unaffected: >= 9.0.5
Unaffected: >= 8.4.9 < 8.4.10
Unaffected: >= 8.3.16 < 8.3.17
Unaffected: >= 8.2.22 < 8.2.23
Unaffected: >= 8.4.10 < 8.4.11
Unaffected: >= 8.3.17 < 8.3.18
Unaffected: >= 8.2.23 < 8.2.24
Unaffected: >= 8.4.11
Unaffected: >= 8.3.18
Architectures: All supported architectures

Package: dev-db/postgresql-base
Vulnerable: < 9.0.5
Unaffected: >= 9.0.5
Unaffected: >= 8.4.9 < 8.4.10
Unaffected: >= 8.3.16 < 8.3.17
Unaffected: >= 8.2.22 < 8.2.23
Unaffected: >= 8.4.10 < 8.4.11
Unaffected: >= 8.3.17 < 8.3.18
Unaffected: >= 8.2.23 < 8.2.24
Unaffected: >= 8.4.11
Unaffected: >= 8.3.18
Architectures: All supported architectures


Description

Multiple vulnerabilities have been discovered in PostgreSQL. Please
review the CVE identifiers referenced below for details.


Impact

A remote authenticated attacker could send a specially crafted SQL query
to a PostgreSQL server with the "intarray" module enabled, possibly
resulting in the execution of arbitrary code with the privileges of the
PostgreSQL server process, or a Denial of Service condition. Furthermore,
a remote authenticated attacker could execute arbitrary Perl code, cause
a Denial of Service condition via different vectors, bypass LDAP
authentication, bypass X.509 certificate validation, gain database
privileges, exploit weak blowfish encryption and possibly cause other
unspecified impact.


Workaround

There is no known workaround at this time.

Resolution

All PostgreSQL 8.2 users should upgrade to the latest 8.2 base version: