| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in PostgreSQL and classified as problematic. Affected by this issue is some unknown functionality of the component SSL Certificate Handler. Performing a manipulation results in config. This vulnerability is known as CVE-2012-0867. No exploit is available. The affected component should be upgraded.
Details
A vulnerability, which was classified as critical, was found in PostgreSQL (Database Software). This affects an unknown part of the component SSL Certificate Handler. The manipulation with an unknown input leads to a config vulnerability. CWE is classifying the issue as CWE-16. This is going to have an impact on confidentiality, and integrity. The summary by CVE is:
PostgreSQL 8.4.x before 8.4.11, 9.0.x before 9.0.7, and 9.1.x before 9.1.3 truncates the common name to only 32 characters when verifying SSL certificates, which allows remote attackers to spoof connections when the host name is exactly 32 characters.
The weakness was published 02/27/2012 (Website). The advisory is shared at postgresql.org. This vulnerability is uniquely identified as CVE-2012-0867 since 01/19/2012. The exploitability is told to be difficult. It is possible to initiate the attack remotely. A authentication is necessary for exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592.004 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 69689 (Amazon Linux AMI : postgresql8 (ALAS-2012-82)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Amazon Linux Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 350665 (Amazon Linux Security Advisory for postgresql8: ALAS-2012-082).
Upgrading to version 9.1.3, 9.0.7, 8.4.11, 8.3.18 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 (69689), SecurityFocus (BID 52188†), OSVDB (79645†), Secunia (SA48107†) and SecurityTracker (ID 1026744†). Similar entries are available at VDB-4666 and VDB-4664. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
- 8.4
- 8.4.1
- 8.4.2
- 8.4.3
- 8.4.4
- 8.4.5
- 8.4.6
- 8.4.7
- 8.4.8
- 8.4.9
- 8.4.10
- 9.0
- 9.0.1
- 9.0.2
- 9.0.3
- 9.0.4
- 9.0.5
- 9.0.6
- 9.1
- 9.1.1
- 9.1.2
License
Website
- Product: https://www.postgresql.org/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.5
VulDB Base Score: 6.8
VulDB Temp Score: 6.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: ConfigCWE: CWE-16
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 69689
Nessus Name: Amazon Linux AMI : postgresql8 (ALAS-2012-82)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
OpenVAS ID: 71146
OpenVAS Name: Debian Security Advisory DSA 2418-1 (postgresql-8.4)
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: PostgreSQL 9.1.3, 9.0.7, 8.4.11, 8.3.18
Timeline
01/19/2012 🔍02/27/2012 🔍
02/27/2012 🔍
02/27/2012 🔍
02/27/2012 🔍
02/27/2012 🔍
02/28/2012 🔍
02/29/2012 🔍
03/07/2012 🔍
07/18/2012 🔍
03/21/2021 🔍
Sources
Product: postgresql.orgAdvisory: postgresql.org
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2012-0867 (🔍)
GCVE (CVE): GCVE-0-2012-0867
GCVE (VulDB): GCVE-100-4665
OVAL: 🔍
SecurityFocus: 52188 - PostgreSQL Multiple Security Vulnerabilities
Secunia: 48107 - PostgreSQL Multiple Vulnerabilities, Less Critical
OSVDB: 79645
SecurityTracker: 1026744 - PostgreSQL Bugs Let Remote Authenticated Users Gain Elevated Privileges, Inject SQL Commands, and Spoof Certificates
Vulnerability Center: 34577 - PostgreSQL Core Server with SSL Support Enabled Allows Connection Spoofing, Medium
See also: 🔍
Entry
Created: 02/29/2012 01:00Updated: 03/21/2021 07:33
Changes: 02/29/2012 01:00 (71), 04/10/2017 10:39 (11), 03/21/2021 07:33 (3)
Complete: 🔍
Cache ID: 216:4A8:103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.