| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in PostgreSQL 9.0/9.1/9.2/9.3/9.4. The impacted element is an unknown function. Performing a manipulation results in information disclosure. This vulnerability is known as CVE-2015-3166. No exploit is available. To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability classified as problematic has been found in PostgreSQL 9.0/9.1/9.2/9.3/9.4 (Database Software). This affects an unknown code. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality.
The weakness was published 05/22/2015 by Noah Misch as PostgreSQL 9.4.2, 9.3.7, 9.2.11, 9.1.16, and 9.0.20 released! as confirmed release notes (Website). It is possible to read the advisory at postgresql.org. This vulnerability is uniquely identified as CVE-2015-3166 since 04/10/2015. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1592 according to MITRE ATT&CK.
The vulnerability scanner Nessus provides a plugin with the ID 83786 (Debian DSA-3269-1 : postgresql-9.1 - security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks. 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. Applying a patch is able to eliminate this problem. The best possible mitigation is suggested to be patching the affected component. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at X-Force (103464), Tenable (83786), SecurityFocus (BID 74790†), SecurityTracker (ID 1032396†) and Vulnerability Center (SBV-52660†). Similar entries are available at VDB-75554, VDB-75556 and VDB-145996. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
Website
- Product: https://www.postgresql.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.2
VulDB Base Score: 5.3
VulDB Temp Score: 4.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Unproven
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 83786
Nessus Name: Debian DSA-3269-1 : postgresql-9.1 - security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
OpenVAS ID: 14611
OpenVAS Name: Amazon Linux Local Check: ALAS-2015-556
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: PostgreSQL 9.0.20/9.1.16/9.2.11/9.3.7/9.4.2
Timeline
04/10/2015 🔍05/22/2015 🔍
05/22/2015 🔍
05/22/2015 🔍
05/26/2015 🔍
05/26/2015 🔍
09/16/2015 🔍
09/17/2015 🔍
05/19/2022 🔍
Sources
Product: postgresql.orgAdvisory: PostgreSQL 9.4.2, 9.3.7, 9.2.11, 9.1.16, and 9.0.20 released!
Researcher: Noah Misch
Status: Confirmed
CVE: CVE-2015-3166 (🔍)
GCVE (CVE): GCVE-0-2015-3166
GCVE (VulDB): GCVE-100-75555
OVAL: 🔍
X-Force: 103464 - PostgreSQL information disclosure
SecurityFocus: 74790 - PostgreSQL CVE-2015-3166 Security Vulnerability
SecurityTracker: 1032396
Vulnerability Center: 52660 - PostgreSQL Remote Information Disclosure due to Improper Check for Failure of the printf(), Medium
See also: 🔍
Entry
Created: 05/26/2015 12:12Updated: 05/19/2022 11:04
Changes: 05/26/2015 12:12 (64), 12/23/2017 13:16 (9), 05/19/2022 10:51 (2), 05/19/2022 10:58 (18), 05/19/2022 11:04 (1)
Complete: 🔍
Cache ID: 216:4D3:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.