PostgreSQL 9.2.1 Query UNION/INTERSET/EXCEPT memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.5 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in PostgreSQL 9.2.1. This issue affects some unknown processing of the component Query. Performing a manipulation of the argument UNION/INTERSET/EXCEPT as part of Eingabe results in memory corruption. No exploit is available. It is recommended to upgrade the affected component.
Details
A vulnerability classified as very critical has been found in PostgreSQL 9.2.1 (Database Software). This affects some unknown processing of the component Query. The manipulation of the argument UNION/INTERSET/EXCEPT as part of a Eingabe leads to a memory corruption vulnerability. CWE is classifying the issue as CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was published 12/06/2012 by Tom Lane as E.3. Release 9.2.2 as not defined changelog entry (Website). It is possible to read the advisory at postgresql.org. The exploitability is told to be difficult. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/21/2019).
Upgrading to version 9.2.2 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the vulnerability database at OSVDB (92956†). 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: 10.0VulDB Meta Temp Score: 9.5
VulDB Base Score: 10.0
VulDB Temp Score: 9.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: 🔍
Exploiting
Class: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: PostgreSQL 9.2.2
Timeline
12/06/2012 🔍12/06/2012 🔍
05/06/2013 🔍
03/21/2019 🔍
Sources
Product: postgresql.orgAdvisory: E.3. Release 9.2.2
Researcher: Tom Lane
Status: Not defined
GCVE (VulDB): GCVE-100-8595
OSVDB: 92956
Entry
Created: 05/06/2013 17:18Updated: 03/21/2019 07:16
Changes: 05/06/2013 17:18 (44), 03/21/2019 07:16 (2)
Complete: 🔍
Committer:
Cache ID: 216:3AD:103
No comments yet. Languages: en.
Please log in to comment.