Bug 237682 (CVE-2007-2138) - CVE-2007-2138 PostgreSQL security-definer function privilege escalation
Summary: CVE-2007-2138 PostgreSQL security-definer function privilege escalation
Alias: CVE-2007-2138
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Tom Lane
QA Contact: David Lawrence
: 237825 (view as bug list)
Depends On:
TreeView+ depends on / blocked
Reported: 2007-04-24 18:46 UTC by Josh Bressers
Modified: 2019-09-29 12:20 UTC (History)
3 users (show)

Fixed In Version: 8.2.4
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2007-06-04 04:15:46 UTC

Attachments (Terms of Use)

Description Josh Bressers 2007-04-24 18:46:32 UTC
+++ This bug was initially created as a clone of Bug #237680 +++

Quoting the PostgreSQL release notes:

    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.

This flaw also affects FC5 and FC7

Comment 1 Tom Lane 2007-04-24 21:53:29 UTC
I've built the following:
F7   postgresql-8.2.4-1.fc7
FC6  postgresql-8.1.9-1.fc6
FC5  postgresql-8.1.9-1.fc5

Comment 2 Lubomir Kundrak 2007-04-25 15:32:19 UTC
*** Bug 156726 has been marked as a duplicate of this bug. ***

Comment 3 Tom Lane 2007-04-25 15:34:47 UTC
*** Bug 237825 has been marked as a duplicate of this bug. ***

Comment 4 Bojan Smojver 2007-04-27 23:08:01 UTC
I see you built the RPMS on the 24th. Any reason why they are not in updates for

Comment 5 Fedora Update System 2007-06-04 04:15:42 UTC
postgresql-8.2.4-1.fc7 has been pushed to the Fedora 7 stable repository.  If problems still persist, please make note of it in this bug report.

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