Rapid7 Vulnerability & Exploit Database

RHSA-2005:433: postgresql security update

Back to Search

RHSA-2005:433: postgresql security update

Severity
8
CVSS
(AV:N/AC:L/Au:N/C:P/I:P/A:P)
Published
05/03/2005
Created
07/25/2018
Added
10/28/2005
Modified
07/12/2017

Description

Updated postgresql packages that fix several security vulnerabilities and risks of data loss are now available. This update has been rated as having moderate security impact by the Red Hat Security Response Team.

PostgreSQL is an advanced Object-Relational database management system (DBMS) that supports almost all SQL constructs (including transactions, subselects and user-defined types and functions). The PostgreSQL community discovered two distinct errors in initial system catalog entries that could allow authorized database users to crash the database and possibly escalate their privileges. The Common Vulnerabilities and Exposures project (cve.mitre.org) has assigned the names CAN-2005-1409 and CAN-2005-1410 to these issues. Although installing this update will protect new (freshly initdb'd) database installations from these errors, administrators MUST TAKE MANUAL ACTION to repair the errors in pre-existing databases. The appropriate procedures are explained at http://www.postgresql.org/docs/8.0/static/release-7-4-8.html for Red Hat Enterprise Linux 4 users, or http://www.postgresql.org/docs/8.0/static/release-7-3-10.html for Red Hat Enterprise Linux 3 users. This update corrects several problems that might occur while trying to upgrade a Red Hat Enterprise Linux 3 installation (containing rh-postgresql packages) to Red Hat Enterprise Linux 4 (containing postgresql packages). These updated packages correctly supersede the rh-postgresql packages. The original release of Red Hat Enterprise Linux 4 failed to initialize the database correctly if started for the first time with SELinux in enforcement mode. This update corrects that problem. If you already have a nonfunctional database in place, shut down the postgresql service if running, install this update, then do "sudo rm -rf /var/lib/pgsql/data" before restarting the postgresql service. This update also solves the problem that the PostgreSQL server might fail to restart after a system reboot, due to a stale lockfile. This update also corrects a problem with wrong error messages in libpq, the postgresql client library. The library would formerly report kernel error messages incorrectly when the locale setting was not C. This update also includes fixes for several other errors, including two race conditions that could result in apparent data inconsistency or actual data loss. All users of PostgreSQL are advised to upgrade to these updated packages and to apply the recommended manual corrections to existing databases.

Solution(s)

  • redhat-upgrade-postgresql
  • redhat-upgrade-postgresql-contrib
  • redhat-upgrade-postgresql-devel
  • redhat-upgrade-postgresql-docs
  • redhat-upgrade-postgresql-jdbc
  • redhat-upgrade-postgresql-libs
  • redhat-upgrade-postgresql-pl
  • redhat-upgrade-postgresql-python
  • redhat-upgrade-postgresql-server
  • redhat-upgrade-postgresql-tcl
  • redhat-upgrade-postgresql-test
  • redhat-upgrade-rh-postgresql
  • redhat-upgrade-rh-postgresql-contrib
  • redhat-upgrade-rh-postgresql-devel
  • redhat-upgrade-rh-postgresql-docs
  • redhat-upgrade-rh-postgresql-jdbc
  • redhat-upgrade-rh-postgresql-libs
  • redhat-upgrade-rh-postgresql-pl
  • redhat-upgrade-rh-postgresql-python
  • redhat-upgrade-rh-postgresql-server
  • redhat-upgrade-rh-postgresql-tcl
  • redhat-upgrade-rh-postgresql-test

With Rapid7 live dashboards, I have a clear view of all the assets on my network, which ones can be exploited, and what I need to do in order to reduce the risk in my environment in real-time. No other tool gives us that kind of value and insight.

– Scott Cheney, Manager of Information Security, Sierra View Medical Center

;