CVE-2013-0255
Last modified
CVE-2013-0255 is a vulnerability of currently unknown severity. PostgreSQL 9.2.x before 9.2.3, 9.1.x before 9.1.8, 9.0.x before 9.0.12, 8.4.x before 8.4.16, and 8.3.x before 8.3.23 does not properly declare the enum_recv function in backend/utils/adt/enum.c, which causes it to be invoked with incorrect arguments and allows remote authenticated users to cause a denial of service (server crash) or read sensitive process memory via a crafted SQL command, which triggers an array index error and an out-of-bounds read.. EPSS estimates a 3.59% chance of exploitation in the next 30 days.
Description
PostgreSQL 9.2.x before 9.2.3, 9.1.x before 9.1.8, 9.0.x before 9.0.12, 8.4.x before 8.4.16, and 8.3.x before 8.3.23 does not properly declare the enum_recv function in backend/utils/adt/enum.c, which causes it to be invoked with incorrect arguments and allows remote authenticated users to cause a denial of service (server crash) or read sensitive process memory via a crafted SQL command, which triggers an array index error and an out-of-bounds read.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Postgresql | Postgresql | 8.3 |
| Postgresql | Postgresql | 8.3.1 |
| Postgresql | Postgresql | 8.3.2 |
| Postgresql | Postgresql | 8.3.3 |
| Postgresql | Postgresql | 8.3.4 |
| Postgresql | Postgresql | 8.3.5 |
| Postgresql | Postgresql | 8.3.6 |
| Postgresql | Postgresql | 8.3.7 |
| Postgresql | Postgresql | 8.3.8 |
| Postgresql | Postgresql | 8.3.9 |
| Postgresql | Postgresql | 8.3.10 |
| Postgresql | Postgresql | 8.3.11 |
| Postgresql | Postgresql | 8.3.12 |
| Postgresql | Postgresql | 8.3.13 |
| Postgresql | Postgresql | 8.3.14 |
| Postgresql | Postgresql | 8.3.15 |
| Postgresql | Postgresql | 8.3.16 |
| Postgresql | Postgresql | 8.3.17 |
| Postgresql | Postgresql | 8.3.18 |
| Postgresql | Postgresql | 8.3.19 |
| Postgresql | Postgresql | 8.3.20 |
| Postgresql | Postgresql | 8.3.21 |
| Postgresql | Postgresql | 8.3.22 |
| Postgresql | Postgresql | 8.4 |
| Postgresql | Postgresql | 8.4.1 |
| Postgresql | Postgresql | 8.4.2 |
| Postgresql | Postgresql | 8.4.3 |
| Postgresql | Postgresql | 8.4.4 |
| Postgresql | Postgresql | 8.4.5 |
| Postgresql | Postgresql | 8.4.6 |
| Postgresql | Postgresql | 8.4.7 |
| Postgresql | Postgresql | 8.4.8 |
| Postgresql | Postgresql | 8.4.9 |
| Postgresql | Postgresql | 8.4.10 |
| Postgresql | Postgresql | 8.4.11 |
| Postgresql | Postgresql | 8.4.12 |
| Postgresql | Postgresql | 8.4.13 |
| Postgresql | Postgresql | 8.4.14 |
| Postgresql | Postgresql | 8.4.15 |
| Postgresql | Postgresql | 9.0 |
| Postgresql | Postgresql | 9.0.1 |
| Postgresql | Postgresql | 9.0.2 |
| Postgresql | Postgresql | 9.0.3 |
| Postgresql | Postgresql | 9.0.4 |
| Postgresql | Postgresql | 9.0.5 |
| Postgresql | Postgresql | 9.0.6 |
| Postgresql | Postgresql | 9.0.7 |
| Postgresql | Postgresql | 9.0.8 |
| Postgresql | Postgresql | 9.0.9 |
| Postgresql | Postgresql | 9.0.10 |
Showing 50 of 59 affected configurations. See NVD for the full list.
References
- http://secunia.com/advisories/51923Vendor Advisory
- http://secunia.com/advisories/51923Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2013-0255?
How severe is CVE-2013-0255?
How do I fix CVE-2013-0255?
Are you affected by CVE-2013-0255?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
