+++ This bug was initially created as a clone of Bug #225493 +++ An authenticated PostgreSQL user has the ability to crash the database server or possibly read arbitrary memory for the server process. This is caused by insufficient type checking for SQL-language functions. CVE-2006-5556 also describes a similar flaw. The description form the PostgreSQL advisory describes it as such: The risk scenarios are exactly the same as above, but the method to exploit the hole is a bit different. The attacker must cause a query plan to be prepared and saved (via PREPARE, or implicitly in a plpgsql function) and then execute an ALTER COLUMN TYPE command to change the type of one of the columns used in the query, and then execute the now-stale query plan. Since ALTER COLUMN TYPE was introduced in PostgreSQL 8.0, older versions are not vulnerable.
removing embargo; public at http://www.postgresql.org/support/security.html
Fix is built in postgresql-8.1.7-1.el5, awaiting RHEL5 0-day updates.
It turns out that the security fix in 8.1.7 broke enough things that it's going to have to be modified. I'm withdrawing postgresql-8.1.7-1.el5 as a candidate for RHEL5 0-day. Upstream is going to spin an 8.1.8 with the fix shortly (probably tonight) and I recommend we go with that instead.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on the solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2007-0068.html