First published: Tue Feb 05 2013(Updated: )
An array index error, leading to out of heap-based buffer bounds read flaw was found in the way PostgreSQL, an advanced Object-Relational database management system (DBMS), performed retrieval of textual form of error message representation when processing certain enumeration types. An unprivileged database user could issue a specially-crafted SQL query that, when processed by the server component of the PostgreSQL service, would lead to denial of service (daemon crash) or disclosure (of certain portions of) server memory.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/PostgreSQL | <9.2.3 | 9.2.3 |
redhat/PostgreSQL | <9.1.8 | 9.1.8 |
redhat/PostgreSQL | <9.0.12 | 9.0.12 |
redhat/PostgreSQL | <8.4.16 | 8.4.16 |
redhat/PostgreSQL | <8.3.23 | 8.3.23 |
PostgreSQL Common | =8.3 | |
PostgreSQL Common | =8.3.1 | |
PostgreSQL Common | =8.3.2 | |
PostgreSQL Common | =8.3.3 | |
PostgreSQL Common | =8.3.4 | |
PostgreSQL Common | =8.3.5 | |
PostgreSQL Common | =8.3.6 | |
PostgreSQL Common | =8.3.7 | |
PostgreSQL Common | =8.3.8 | |
PostgreSQL Common | =8.3.9 | |
PostgreSQL Common | =8.3.10 | |
PostgreSQL Common | =8.3.11 | |
PostgreSQL Common | =8.3.12 | |
PostgreSQL Common | =8.3.13 | |
PostgreSQL Common | =8.3.14 | |
PostgreSQL Common | =8.3.15 | |
PostgreSQL Common | =8.3.16 | |
PostgreSQL Common | =8.3.17 | |
PostgreSQL Common | =8.3.18 | |
PostgreSQL Common | =8.3.19 | |
PostgreSQL Common | =8.3.20 | |
PostgreSQL Common | =8.3.21 | |
PostgreSQL Common | =8.3.22 | |
PostgreSQL Common | =8.4 | |
PostgreSQL Common | =8.4.1 | |
PostgreSQL Common | =8.4.2 | |
PostgreSQL Common | =8.4.3 | |
PostgreSQL Common | =8.4.4 | |
PostgreSQL Common | =8.4.5 | |
PostgreSQL Common | =8.4.6 | |
PostgreSQL Common | =8.4.7 | |
PostgreSQL Common | =8.4.8 | |
PostgreSQL Common | =8.4.9 | |
PostgreSQL Common | =8.4.10 | |
PostgreSQL Common | =8.4.11 | |
PostgreSQL Common | =8.4.12 | |
PostgreSQL Common | =8.4.13 | |
PostgreSQL Common | =8.4.14 | |
PostgreSQL Common | =8.4.15 | |
PostgreSQL Common | =9.0 | |
PostgreSQL Common | =9.0.1 | |
PostgreSQL Common | =9.0.2 | |
PostgreSQL Common | =9.0.3 | |
PostgreSQL Common | =9.0.4 | |
PostgreSQL Common | =9.0.5 | |
PostgreSQL Common | =9.0.6 | |
PostgreSQL Common | =9.0.7 | |
PostgreSQL Common | =9.0.8 | |
PostgreSQL Common | =9.0.9 | |
PostgreSQL Common | =9.0.10 | |
PostgreSQL Common | =9.0.11 | |
PostgreSQL Common | =9.1 | |
PostgreSQL Common | =9.1.1 | |
PostgreSQL Common | =9.1.2 | |
PostgreSQL Common | =9.1.3 | |
PostgreSQL Common | =9.1.4 | |
PostgreSQL Common | =9.1.5 | |
PostgreSQL Common | =9.1.6 | |
PostgreSQL Common | =9.1.7 | |
PostgreSQL Common | =9.2 | |
PostgreSQL Common | =9.2.1 | |
PostgreSQL Common | =9.2.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-0255 has been classified with a moderate severity level.
To fix CVE-2013-0255, upgrade PostgreSQL to versions 9.2.3, 9.1.8, 9.0.12, 8.4.16, or 8.3.23 or later.
CVE-2013-0255 affects PostgreSQL versions 8.3 up to 8.3.22, 8.4 up to 8.4.15, 9.0 up to 9.0.11, and 9.1 up to 9.1.7.
Using vulnerable versions affected by CVE-2013-0255 in production environments is not recommended due to potential security risks.
Exploitation of CVE-2013-0255 can lead to unauthorized access and manipulation of the PostgreSQL database, putting data integrity at risk.