PostgreSQL up to 9.3.20/9.4.15/9.5.10/9.6.6 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.
6.0$0-$5k0.00

Summaryinfo

A vulnerability described as critical has been identified in PostgreSQL up to 9.3.20/9.4.15/9.5.10/9.6.6. This affects an unknown part. Executing a manipulation can lead to access control. The identification of this vulnerability is CVE-2018-1053. The attack can only be executed locally. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as critical was found in PostgreSQL up to 9.3.20/9.4.15/9.5.10/9.6.6 (Database Software). This vulnerability affects an unknown code block. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-264. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

In postgresql 9.3.x before 9.3.21, 9.4.x before 9.4.16, 9.5.x before 9.5.11, 9.6.x before 9.6.7 and 10.x before 10.2, pg_upgrade creates file in current working directory containing the output of `pg_dumpall -g` under umask which was in effect when the user invoked pg_upgrade, and not under 0077 which is normally used for other temporary files. This can allow an authenticated attacker to read or modify the one file, which may contain encrypted or unencrypted database passwords. The attack is infeasible if a directory mode blocks the attacker searching the current working directory or if the prevailing umask blocks the attacker opening the file.

The bug was discovered 02/08/2018. The weakness was shared 02/09/2018 (Website). The advisory is shared for download at postgresql.org. This vulnerability was named CVE-2018-1053 since 12/04/2017. The attack needs to be approached locally. The requirement for exploitation is a single authentication. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1068.

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 106941 (SUSE SLES11 Security Update : postgresql94 (SUSE-SU-2018:0506-1)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 170891 (OpenSUSE Security Update for postgresql95 (openSUSE-SU-2018:0529-1)).

Upgrading to version 9.3.21, 9.4.16, 9.5.11 or 9.6.7 eliminates this vulnerability. A possible mitigation has been published 2 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (106941) and SecurityFocus (BID 102986†). The entry VDB-113103 is related to this item. VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.1
VulDB Meta Temp Score: 6.0

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 7.0
NVD Vector: 🔍

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: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 106941
Nessus Name: SUSE SLES11 Security Update : postgresql94 (SUSE-SU-2018:0506-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 880752
OpenVAS Name: SuSE Update for postgresql95 openSUSE-SU-2018:0529-1 (postgresql95)
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 9.3.21/9.4.16/9.5.11/9.6.7

Timelineinfo

12/04/2017 🔍
02/08/2018 +66 days 🔍
02/08/2018 +0 days 🔍
02/09/2018 +1 days 🔍
02/09/2018 +0 days 🔍
02/10/2018 +1 days 🔍
02/21/2018 +11 days 🔍
02/22/2018 +1 days 🔍
02/06/2023 +1810 days 🔍

Sourcesinfo

Product: postgresql.org

Advisory: RHSA-2018:2511
Status: Not defined
Confirmation: 🔍

CVE: CVE-2018-1053 (🔍)
GCVE (CVE): GCVE-0-2018-1053
GCVE (VulDB): GCVE-100-113104
SecurityFocus: 102986 - PostgreSQL CVE-2018-1053 Insecure Temporary File Creation Vulnerability

See also: 🔍

Entryinfo

Created: 02/10/2018 09:01
Updated: 02/06/2023 11:39
Changes: 02/10/2018 09:01 (76), 01/03/2020 16:51 (5), 02/06/2023 11:39 (4)
Complete: 🔍
Cache ID: 216::103

VulDB is the best source for vulnerability data and more expert information about this specific topic.

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!