PostgreSQL up to 9.1.20/9.2.15/9.3.11/9.4.6/9.5.1 Row Level Security Policy 7pk security

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

Summaryinfo

A vulnerability has been found in PostgreSQL up to 9.1.20/9.2.15/9.3.11/9.4.6/9.5.1 and classified as problematic. Affected by this vulnerability is an unknown functionality of the component Row Level Security Policy Handler. Performing a manipulation results in 7pk security. This vulnerability is cataloged as CVE-2016-2193. It is possible to initiate the attack remotely. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in PostgreSQL up to 9.1.20/9.2.15/9.3.11/9.4.6/9.5.1 (Database Software). It has been classified as critical. This affects an unknown part of the component Row Level Security Policy Handler. The manipulation with an unknown input leads to a 7pk security vulnerability. CWE is classifying the issue as CWE-254. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

PostgreSQL before 9.5.x before 9.5.2 does not properly maintain row-security status in cached plans, which might allow attackers to bypass intended access restrictions by leveraging a session that performs queries as more than one role.

The weakness was shared 03/31/2016 as 2016-03-31 Security Update Release as confirmed news (Website). The advisory is shared at postgresql.org. This vulnerability is uniquely identified as CVE-2016-2193 since 01/28/2016. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1211 for this issue.

The vulnerability scanner Nessus provides a plugin with the ID 90423 (PostgreSQL 9.5.x < 9.5.2 Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Databases and running in the context l.

Upgrading to version 9.1.21, 9.2.16, 9.3.12, 9.4.7 or 9.5.2 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (90423), SecurityFocus (BID 85784†) and SecurityTracker (ID 1035468†). The entries VDB-81610 and VDB-82085 are related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

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: 7.1

VulDB Base Score: 7.1
VulDB Temp Score: 6.8
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: 7pk security
CWE: CWE-254
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: 90423
Nessus Name: PostgreSQL 9.5.x < 9.5.2 Multiple Vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 11865
OpenVAS Name: PostgreSQL Multiple Vulnerabilities - Apr16 (Windows)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

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

Upgrade: PostgreSQL 9.1.21/9.2.16/9.3.12/9.4.7/9.5.2
Patch: db69e58a0642ef7fa46d62f6c4cf2460c3a1b41b

Timelineinfo

01/28/2016 🔍
03/31/2016 +62 days 🔍
03/31/2016 +0 days 🔍
04/04/2016 +4 days 🔍
04/06/2016 +2 days 🔍
04/08/2016 +1 days 🔍
04/11/2016 +3 days 🔍
07/12/2022 +2283 days 🔍

Sourcesinfo

Product: postgresql.org

Advisory: 2016-03-31 Security Update Release
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-2193 (🔍)
GCVE (CVE): GCVE-0-2016-2193
GCVE (VulDB): GCVE-100-81609
SecurityFocus: 85784
SecurityTracker: 1035468

See also: 🔍

Entryinfo

Created: 04/06/2016 09:08
Updated: 07/12/2022 09:19
Changes: 04/06/2016 09:08 (57), 09/24/2018 08:59 (22), 07/12/2022 09:19 (4)
Complete: 🔍
Cache ID: 216:692:103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!