| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in PostgreSQL 7.3.18/7.4.16/8.0.10/8.1.6/8.2.1. This affects an unknown part. Performing a manipulation results in access control. This vulnerability is reported as CVE-2007-2138. No exploit exists. It is recommended to upgrade the affected component.
Details
A vulnerability was found in PostgreSQL 7.3.18/7.4.16/8.0.10/8.1.6/8.2.1 (Database Software). It has been classified as critical. This affects some unknown processing. The manipulation with an unknown input leads to a access control vulnerability. CWE is classifying the issue as CWE-264. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Untrusted search path vulnerability in PostgreSQL before 7.3.19, 7.4.x before 7.4.17, 8.0.x before 8.0.13, 8.1.x before 8.1.9, and 8.2.x before 8.2.4 allows remote authenticated users, when permitted to call a SECURITY DEFINER function, to gain the privileges of the function owner, related to "search_path settings."
The bug was discovered 04/23/2007. The weakness was disclosed 04/24/2007 (Website). The advisory is shared at postgresql.org. This vulnerability is uniquely identified as CVE-2007-2138 since 04/18/2007. It is possible to initiate the attack remotely. Required for exploitation is a authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.
It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 67488 (Oracle Linux 3 / 4 / 5 : postgresql (ELSA-2007-0336)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Oracle Linux Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 19507 (PostgreSQL SECURITY DEFINER Function Local Privilege Escalation Vulnerability).
Upgrading to version 7.3.19 eliminates this vulnerability. A possible mitigation has been published 3 months after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at X-Force (33842), Tenable (67488), SecurityFocus (BID 23618†), OSVDB (34903†) and Secunia (SA25019†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
Website
- Product: https://www.postgresql.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-264
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 67488
Nessus Name: Oracle Linux 3 / 4 / 5 : postgresql (ELSA-2007-0336)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍
OpenVAS ID: 58358
OpenVAS Name: Debian Security Advisory DSA 1309-1 (postgresql-8.1)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: PostgreSQL 7.3.19
Timeline
04/18/2007 🔍04/23/2007 🔍
04/24/2007 🔍
04/24/2007 🔍
04/24/2007 🔍
04/24/2007 🔍
04/24/2007 🔍
04/27/2007 🔍
05/06/2007 🔍
06/26/2007 🔍
07/12/2013 🔍
03/13/2015 🔍
06/08/2025 🔍
Sources
Product: postgresql.orgAdvisory: postgresql.org
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2007-2138 (🔍)
GCVE (CVE): GCVE-0-2007-2138
GCVE (VulDB): GCVE-100-36357
OVAL: 🔍
X-Force: 33842
SecurityFocus: 23618 - PostgreSQL SECURITY DEFINER Function Local Privilege Escalation Vulnerability
Secunia: 25019
OSVDB: 34903 - CVE-2007-2138 - PostgreSQL - Untrusted Search Path Issue
SecurityTracker: 1017974
Vulnerability Center: 14985 - PostgreSQL Untrusted Search Path Vulnerability, Low
Vupen: ADV-2007-1497
Entry
Created: 03/13/2015 14:56Updated: 06/08/2025 22:15
Changes: 03/13/2015 14:56 (81), 07/18/2019 16:21 (5), 06/08/2025 22:15 (22)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.