CVE-2013-0255: Input Validation

Published Feb 5, 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.

Other sources

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 enumrecv 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.

MITRE

Affected Software

67 affected componentsFixes available
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 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
PostgreSQL postgresql=9.0.11
PostgreSQL postgresql=9.1
PostgreSQL postgresql=9.1.1
PostgreSQL postgresql=9.1.2
PostgreSQL postgresql=9.1.3
PostgreSQL postgresql=9.1.4
PostgreSQL postgresql=9.1.5
PostgreSQL postgresql=9.1.6
PostgreSQL postgresql=9.1.7
PostgreSQL postgresql=9.2
PostgreSQL postgresql=9.2.1
PostgreSQL postgresql=9.2.2

Event History

Feb 5, 2013
Data Sourced
via Red Hat·01:33 PM
DescriptionSeverityAffected Software
Feb 13, 2013
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2013-0255?

CVE-2013-0255 has been classified with a moderate severity level.

2

How do I fix CVE-2013-0255?

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.

3

What versions of PostgreSQL are affected by CVE-2013-0255?

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.

4

Is it safe to use CVE-2013-0255 vulnerable versions in production?

Using vulnerable versions affected by CVE-2013-0255 in production environments is not recommended due to potential security risks.

5

What can happen if CVE-2013-0255 is exploited?

Exploitation of CVE-2013-0255 can lead to unauthorized access and manipulation of the PostgreSQL database, putting data integrity at risk.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203