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.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Postgresql | Postgresql | 8.3 (including) | 8.3 (including) |
| Postgresql | Postgresql | 8.3.1 (including) | 8.3.1 (including) |
| Postgresql | Postgresql | 8.3.2 (including) | 8.3.2 (including) |
| Postgresql | Postgresql | 8.3.3 (including) | 8.3.3 (including) |
| Postgresql | Postgresql | 8.3.4 (including) | 8.3.4 (including) |
| Postgresql | Postgresql | 8.3.5 (including) | 8.3.5 (including) |
| Postgresql | Postgresql | 8.3.6 (including) | 8.3.6 (including) |
| Postgresql | Postgresql | 8.3.7 (including) | 8.3.7 (including) |
| Postgresql | Postgresql | 8.3.8 (including) | 8.3.8 (including) |
| Postgresql | Postgresql | 8.3.9 (including) | 8.3.9 (including) |
| Postgresql | Postgresql | 8.3.10 (including) | 8.3.10 (including) |
| Postgresql | Postgresql | 8.3.11 (including) | 8.3.11 (including) |
| Postgresql | Postgresql | 8.3.12 (including) | 8.3.12 (including) |
| Postgresql | Postgresql | 8.3.13 (including) | 8.3.13 (including) |
| Postgresql | Postgresql | 8.3.14 (including) | 8.3.14 (including) |
| Postgresql | Postgresql | 8.3.15 (including) | 8.3.15 (including) |
| Postgresql | Postgresql | 8.3.16 (including) | 8.3.16 (including) |
| Postgresql | Postgresql | 8.3.17 (including) | 8.3.17 (including) |
| Postgresql | Postgresql | 8.3.18 (including) | 8.3.18 (including) |
| Postgresql | Postgresql | 8.3.19 (including) | 8.3.19 (including) |
| Postgresql | Postgresql | 8.3.20 (including) | 8.3.20 (including) |
| Postgresql | Postgresql | 8.3.21 (including) | 8.3.21 (including) |
| Postgresql | Postgresql | 8.3.22 (including) | 8.3.22 (including) |
| Red Hat Enterprise Linux 5 | RedHat | postgresql84-0:8.4.18-1.el5_10 | * |
| Red Hat Enterprise Linux 6 | RedHat | postgresql-0:8.4.18-1.el6_4 | * |
| Postgresql-8.2 | Ubuntu | hardy | * |
| Postgresql-8.3 | Ubuntu | hardy | * |
| Postgresql-8.3 | Ubuntu | upstream | * |
| Postgresql-8.4 | Ubuntu | lucid | * |
| Postgresql-8.4 | Ubuntu | oneiric | * |
| Postgresql-8.4 | Ubuntu | precise | * |
| Postgresql-8.4 | Ubuntu | upstream | * |
| Postgresql-9.1 | Ubuntu | oneiric | * |
| Postgresql-9.1 | Ubuntu | precise | * |
| Postgresql-9.1 | Ubuntu | quantal | * |
| Postgresql-9.1 | Ubuntu | upstream | * |
Input validation is a frequently-used technique for checking potentially dangerous inputs in order to ensure that the inputs are safe for processing within the code, or when communicating with other components. Input can consist of:
Data can be simple or structured. Structured data can be composed of many nested layers, composed of combinations of metadata and raw data, with other simple or structured data. Many properties of raw data or metadata may need to be validated upon entry into the code, such as:
Implied or derived properties of data must often be calculated or inferred by the code itself. Errors in deriving properties may be considered a contributing factor to improper input validation.