PostgreSQL up to 9.0.19/9.1.15/9.2.10/9.3.6/9.4.1 Error Message information disclosure

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 was found in PostgreSQL up to 9.0.19/9.1.15/9.2.10/9.3.6/9.4.1. It has been classified as problematic. Impacted is an unknown function of the component Error Message Handler. The manipulation leads to information disclosure. This vulnerability is uniquely identified as CVE-2015-3167. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in PostgreSQL up to 9.0.19/9.1.15/9.2.10/9.3.6/9.4.1 (Database Software). It has been rated as problematic. This issue affects an unknown code block of the component Error Message Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. Using CWE to declare the problem leads to CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. Impacted is confidentiality. The summary by CVE is:

contrib/pgcrypto in PostgreSQL before 9.0.20, 9.1.x before 9.1.16, 9.2.x before 9.2.11, 9.3.x before 9.3.7, and 9.4.x before 9.4.2 uses different error responses when an incorrect key is used, which makes it easier for attackers to obtain the key via a brute force attack.

The bug was discovered 05/22/2015. The weakness was disclosed 11/20/2019. The identification of this vulnerability is CVE-2015-3167 since 04/10/2015. The exploitation is known to be difficult. 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 T1592 for this issue.

The vulnerability was handled as a non-public zero-day exploit for at least 38 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 84464 (Oracle Linux 6 / 7 : postgresql (ELSA-2015-1194)), 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 350146 (Amazon Linux Security Advisory for postgresql8: ALAS-2015-556).

Upgrading to version 9.0.20, 9.1.16, 9.2.11, 9.3.7 or 9.4.2 eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (84464) and SecurityFocus (BID 74787†). The entries VDB-75554, VDB-75556 and VDB-145996 are pretty similar. 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: 5.6
VulDB Meta Temp Score: 5.5

VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.5
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 84464
Nessus Name: Oracle Linux 6 / 7 : postgresql (ELSA-2015-1194)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 14611
OpenVAS Name: Amazon Linux Local Check: ALAS-2015-556
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: PostgreSQL 9.0.20/9.1.16/9.2.11/9.3.7/9.4.2

Timelineinfo

04/10/2015 🔍
05/22/2015 +42 days 🔍
06/29/2015 +38 days 🔍
06/30/2015 +1 days 🔍
11/20/2019 +1604 days 🔍
11/21/2019 +1 days 🔍
11/26/2024 +1832 days 🔍

Sourcesinfo

Product: postgresql.org

Advisory: RHSA-2015:1194
Status: Confirmed

CVE: CVE-2015-3167 (🔍)
GCVE (CVE): GCVE-0-2015-3167
GCVE (VulDB): GCVE-100-145997

OVAL: 🔍

SecurityFocus: 74787

See also: 🔍

Entryinfo

Created: 11/21/2019 07:54
Updated: 11/26/2024 05:45
Changes: 11/21/2019 07:54 (42), 11/21/2019 07:59 (30), 02/23/2024 22:38 (5), 02/23/2024 22:53 (1), 11/26/2024 05:45 (18)
Complete: 🔍
Cache ID: 216:9EF: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 want to use VulDB in your project?

Use the official API to access entries easily!