PostgreSQL up to 8.1.3 Multi-Byte Character sql injection

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

Summaryinfo

A vulnerability was found in PostgreSQL. It has been rated as critical. The affected element is an unknown function of the component Multi-Byte Character Handler. The manipulation leads to sql injection. This vulnerability is documented as CVE-2006-2313. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as critical, has been found in PostgreSQL (Database Software). This issue affects an unknown function of the component Multi-Byte Character Handler. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

PostgreSQL 8.1.x before 8.1.4, 8.0.x before 8.0.8, 7.4.x before 7.4.13, 7.3.x before 7.3.15, and earlier versions allows context-dependent attackers to bypass SQL injection protection methods in applications via invalid encodings of multibyte characters, aka one variant of "Encoding-Based SQL Injection."

The bug was discovered 05/23/2006. The weakness was released 05/24/2006 by Akio Ishida with Developer Team (Website). The advisory is shared at archives.postgresql.org. The identification of this vulnerability is CVE-2006-2313 since 05/11/2006. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1505 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 $25k-$100k. The vulnerability scanner Nessus provides a plugin with the ID 21670 (Mandrake Linux Security Advisory : postgresql (MDKSA-2006:098)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Mandriva Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 19206 (PostgreSQL Multibyte Character Encoding SQL Injection Vulnerabilities).

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 2 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (26627), Tenable (21670), SecurityFocus (BID 18092†), OSVDB (25730†) and Secunia (SA21001†). Entries connected to this vulnerability are available at VDB-28621 and VDB-30399. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 6.6

VulDB Base Score: 7.3
VulDB Temp Score: 6.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Sql injection
CWE: CWE-89 / CWE-74 / CWE-707
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: 21670
Nessus Name: Mandrake Linux Security Advisory : postgresql (MDKSA-2006:098)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 56857
OpenVAS Name: Debian Security Advisory DSA 1087-1 (postgresql)
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: 🔍

Patch: postgresql.org

Timelineinfo

05/11/2006 🔍
05/23/2006 +12 days 🔍
05/23/2006 +0 days 🔍
05/24/2006 +1 days 🔍
05/24/2006 +0 days 🔍
05/24/2006 +0 days 🔍
05/24/2006 +0 days 🔍
05/24/2006 +0 days 🔍
05/30/2006 +5 days 🔍
06/03/2006 +4 days 🔍
06/08/2006 +5 days 🔍
07/10/2006 +32 days 🔍
06/19/2019 +4727 days 🔍

Sourcesinfo

Product: postgresql.org

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

CVE: CVE-2006-2313 (🔍)
GCVE (CVE): GCVE-0-2006-2313
GCVE (VulDB): GCVE-100-2261

OVAL: 🔍

X-Force: 26627 - PostgreSQL encoded multibyte SQL injection, Medium Risk
SecurityFocus: 18092 - PostgreSQL Multibyte Character Encoding SQL Injection Vulnerabilities
Secunia: 21001 - Gentoo update for postgresql, Moderately Critical
OSVDB: 25730 - PostgreSQL Invalidly-encoded Multibyte Character String Escaping Bypass
SecurityTracker: 1016142
Vulnerability Center: 11612 - PostgreSQL Allows Bypassing of SQL Injection Protection Methods, Medium
Vupen: ADV-2006-1941

See also: 🔍

Entryinfo

Created: 05/30/2006 12:11
Updated: 06/19/2019 09:20
Changes: 05/30/2006 12:11 (104), 06/19/2019 09:20 (1)
Complete: 🔍
Cache ID: 216:D03:103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!