PostgreSQL 8.1.0/8.1.1/8.1.2 Error SET COMMAND access control

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.
5.5$0-$5k0.00

Summaryinfo

A vulnerability marked as problematic has been reported in PostgreSQL 8.1.0/8.1.1/8.1.2. This impacts the function SET COMMAND of the component Error Handler. Performing a manipulation results in access control. This vulnerability is known as CVE-2006-0553. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, was found in PostgreSQL 8.1.0/8.1.1/8.1.2 (Database Software). This affects the function SET COMMAND of the component Error Handler. 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:

PostgreSQL 8.1.0 through 8.1.2 allows authenticated database users to gain additional privileges via "knowledge of the backend protocol" using a crafted SET ROLE to other database users, a different vulnerability than CVE-2006-0678.

The weakness was published 02/15/2006 by Akio Ishida (Website). It is possible to read the advisory at archives.postgresql.org. This vulnerability is uniquely identified as CVE-2006-0553 since 02/05/2006. It is possible to initiate the attack remotely. A authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.

It is declared as proof-of-concept. The vulnerability scanner Nessus provides a plugin with the ID 21384 (FreeBSD : postgresql81-server -- SET ROLE privilege escalation (0b2b4b4d-a07c-11da-be0a-000c6ec775d9)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks and running in the context l.

Upgrading eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at postgresql.org. The best possible mitigation is suggested to be upgrading to the latest version. 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 (24718), Tenable (21384), SecurityFocus (BID 16649†), OSVDB (23223†) and Secunia (SA18890†). Similar entries are available at VDB-2056 and VDB-28702. Be aware that VulDB is the high quality source 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: 6.3
VulDB Meta Temp Score: 5.5

VulDB Base Score: 6.3
VulDB Temp Score: 5.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Access control
CWE: 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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 21384
Nessus Name: FreeBSD : postgresql81-server -- SET ROLE privilege escalation (0b2b4b4d-a07c-11da-be0a-000c6ec775d9)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 56319
OpenVAS Name: FreeBSD Ports: postgresql-server
OpenVAS File: 🔍
OpenVAS Family: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
Exposure Time: 🔍

Patch: postgresql.org

Timelineinfo

02/05/2006 🔍
02/14/2006 +9 days 🔍
02/14/2006 +0 days 🔍
02/15/2006 +1 days 🔍
02/15/2006 +0 days 🔍
02/15/2006 +0 days 🔍
02/18/2006 +2 days 🔍
02/20/2006 +2 days 🔍
05/13/2006 +82 days 🔍
01/20/2025 +6827 days 🔍

Sourcesinfo

Product: postgresql.org

Advisory: archives.postgresql.org
Researcher: Akio Ishida
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2006-0553 (🔍)
GCVE (CVE): GCVE-0-2006-0553
GCVE (VulDB): GCVE-100-2055
CERT: 🔍
X-Force: 24718 - PostgreSQL SET ROLE command privilege elevation, Medium Risk
SecurityFocus: 16649 - PostgreSQL Remote SET ROLE Privilege Escalation Vulnerability
Secunia: 18890 - PostgreSQL Privilege Escalation and Denial of Service, Less Critical
OSVDB: 23223 - PostgreSQL SET ROLE Crafted Argument Privilege Escalation
SecurityTracker: 1015636 - PostgreSQL SET ROLE Validation Error Lets Remote Authenticated Users Obtain Elevated Privileges
Vupen: ADV-2006-0605

See also: 🔍

Entryinfo

Created: 02/20/2006 10:31
Updated: 01/20/2025 03:11
Changes: 02/20/2006 10:31 (88), 06/07/2017 14:55 (5), 03/12/2021 14:12 (3), 01/20/2025 03:11 (15)
Complete: 🔍
Cache ID: 216:D12:103

Be aware that VulDB is the high quality source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!