Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 225493 - CVE-2007-0555 PostgreSQL arbitrary memory read flaw
Summary: CVE-2007-0555 PostgreSQL arbitrary memory read flaw
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: postgresql
Version: 4.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Tom Lane
QA Contact: David Lawrence
Whiteboard: reported=20070129,source=redhat,impac...
Depends On:
TreeView+ depends on / blocked
Reported: 2007-01-30 21:50 UTC by Josh Bressers
Modified: 2013-07-03 03:12 UTC (History)
3 users (show)

Fixed In Version: RHSA-2007-0064
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-02-07 18:25:01 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2007:0064 normal SHIPPED_LIVE Moderate: postgresql security update 2007-02-07 18:24:28 UTC

Description Josh Bressers 2007-01-30 21:50:52 UTC
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.

Comment 1 Josh Bressers 2007-01-30 22:04:21 UTC
This flaw also affects RHEL3

Comment 2 Tom Lane 2007-02-04 22:26:28 UTC
Note that in RHEL3, the relevant package is rh-postgresql ... we don't ship a plain "postgresql" package in 
that branch, for long-obsolete reasons.

Comment 4 Mark J. Cox 2007-02-05 11:32:23 UTC
removing embargo; public at

Comment 7 Red Hat Bugzilla 2007-02-07 18:25:02 UTC
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.

Note You need to log in before you can comment on or make changes to this bug.