Bug 237681 - CVE-2007-2138 PostgreSQL security-definer function privilege escalation
CVE-2007-2138 PostgreSQL security-definer function privilege escalation
Status: CLOSED ERRATA
Product: Red Hat Web Application Stack
Classification: Retired
Component: postgresql (Show other bugs)
v1
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tom Lane
Gurhan Ozen
impact=moderate,public=20070423,repor...
: Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-24 14:42 EDT by Josh Bressers
Modified: 2013-11-03 20:32 EST (History)
2 users (show)

See Also:
Fixed In Version: RHSA-2007-0337
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-05-03 08:35:07 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Josh Bressers 2007-04-24 14:42:40 EDT
+++ This bug was initially created as a clone of Bug #237680 +++

Quoting the PostgreSQL release notes:
http://www.postgresql.org/docs/8.2/static/release-8-2-4.html

    Support explicit placement of the temporary-table schema within search_path, 
    and disable searching it for functions and operators (Tom)

    This is needed to allow a security-definer function to set a truly secure 
    value of search_path. Without it, an unprivileged SQL user can use temporary 
    objects to execute code with the privileges of the security-definer function 
    (CVE-2007-2138). See CREATE FUNCTION for more information.
Comment 6 Red Hat Bugzilla 2007-05-03 08:35:16 EDT
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-0337.html

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