PostgreSQL prior 8.0 improper authentication

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.6$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in PostgreSQL. The impacted element is an unknown function. Performing a manipulation results in improper authentication. This vulnerability was named CVE-2007-6601. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in PostgreSQL (Database Software). It has been classified as critical. This affects an unknown code. The manipulation with an unknown input leads to a improper authentication vulnerability. CWE is classifying the issue as CWE-287. When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

The DBLink module in PostgreSQL 8.2 before 8.2.6, 8.1 before 8.1.11, 8.0 before 8.0.15, 7.4 before 7.4.19, and 7.3 before 7.3.21, when local trust or ident authentication is used, allows remote attackers to gain privileges via unspecified vectors. NOTE: this issue exists because of an incomplete fix for CVE-2007-3278.

The bug was discovered 01/06/2008. The weakness was presented 01/09/2008 (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is uniquely identified as CVE-2007-6601 since 12/31/2007. The exploitability is told to be easy. Attacking locally is a requirement. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.

It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 3 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 29933 (CentOS 4 / 5 : postgresql (CESA-2008:0038)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CentOS Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 165667 (SUSE Enterprise Linux Security Update PostgreSQL Security Issues (SUSE-SA:2008:005)).

Upgrading to version 8.0 eliminates this vulnerability. A possible mitigation has been published 3 days after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (39500), Tenable (29933), SecurityFocus (BID 27163†), OSVDB (40903†) and Secunia (SA28359†). See VDB-37348, VDB-40442, VDB-40441 and VDB-40435 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.4
VulDB Meta Temp Score: 7.6

VulDB Base Score: 8.4
VulDB Temp Score: 7.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Improper authentication
CWE: CWE-287
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 29933
Nessus Name: CentOS 4 / 5 : postgresql (CESA-2008:0038)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 60178
OpenVAS Name: Debian Security Advisory DSA 1460-1 (postgresql-8.1)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: PostgreSQL 8.0

Timelineinfo

12/31/2007 🔍
01/06/2008 +6 days 🔍
01/06/2008 +0 days 🔍
01/07/2008 +1 days 🔍
01/07/2008 +0 days 🔍
01/09/2008 +2 days 🔍
01/09/2008 +0 days 🔍
01/12/2008 +3 days 🔍
01/14/2008 +2 days 🔍
01/20/2008 +6 days 🔍
03/16/2015 +2612 days 🔍
08/03/2019 +1601 days 🔍

Sourcesinfo

Product: postgresql.org

Advisory: securityfocus.com⛔
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2007-6601 (🔍)
GCVE (CVE): GCVE-0-2007-6601
GCVE (VulDB): GCVE-100-40443

OVAL: 🔍

X-Force: 39500
SecurityFocus: 27163 - PostgreSQL Multiple Privilege Escalation and Denial of Service Vulnerabilities
Secunia: 28359
OSVDB: 40903 - CVE-2007-6601 - PostgreSQL - Privilege Escalation Issue
SecurityTracker: 1019157
Vulnerability Center: 17392 - PostgreSQL DBLink Module Remote Privilege Escalation, High
Vupen: ADV-2008-0061

See also: 🔍

Entryinfo

Created: 03/16/2015 13:43
Updated: 08/03/2019 18:04
Changes: 03/16/2015 13:43 (74), 08/03/2019 18:04 (12)
Complete: 🔍
Cache ID: 216:80E:103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!