CVE-2007-0556
Last modified
CVE-2007-0556 is a vulnerability of currently unknown severity. The query planner in PostgreSQL before 8.0.11, 8.1 before 8.1.7, and 8.2 before 8.2.2 does not verify that a table is compatible with a "previously made query plan," which allows remote authenticated users to cause a denial of service (server crash) and possibly access database content via an "ALTER COLUMN TYPE" SQL statement, which can be leveraged to read arbitrary memory from the server.. EPSS estimates a 2.94% chance of exploitation in the next 30 days.
Description
The query planner in PostgreSQL before 8.0.11, 8.1 before 8.1.7, and 8.2 before 8.2.2 does not verify that a table is compatible with a "previously made query plan," which allows remote authenticated users to cause a denial of service (server crash) and possibly access database content via an "ALTER COLUMN TYPE" SQL statement, which can be leveraged to read arbitrary memory from the server.
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Postgresql | Postgresql | 1.0 |
| Postgresql | Postgresql | 1.01 |
| Postgresql | Postgresql | 1.02 |
| Postgresql | Postgresql | 1.09 |
| Postgresql | Postgresql | 6.0 |
| Postgresql | Postgresql | 6.1 |
| Postgresql | Postgresql | 6.1.1 |
| Postgresql | Postgresql | 6.2 |
| Postgresql | Postgresql | 6.2.1 |
| Postgresql | Postgresql | 6.3 |
| Postgresql | Postgresql | 6.3.1 |
| Postgresql | Postgresql | 6.3.2 |
| Postgresql | Postgresql | 6.4 |
| Postgresql | Postgresql | 6.4.1 |
| Postgresql | Postgresql | 6.4.2 |
| Postgresql | Postgresql | 6.5 |
| Postgresql | Postgresql | 6.5.1 |
| Postgresql | Postgresql | 6.5.2 |
| Postgresql | Postgresql | 6.5.3 |
| Postgresql | Postgresql | 7.0 |
| Postgresql | Postgresql | 7.0.1 |
| Postgresql | Postgresql | 7.0.2 |
| Postgresql | Postgresql | 7.0.3 |
| Postgresql | Postgresql | 7.1 |
| Postgresql | Postgresql | 7.1.1 |
| Postgresql | Postgresql | 7.1.2 |
| Postgresql | Postgresql | 7.1.3 |
| Postgresql | Postgresql | 7.2 |
| Postgresql | Postgresql | 7.2.1 |
| Postgresql | Postgresql | 7.2.2 |
| Postgresql | Postgresql | 7.2.3 |
| Postgresql | Postgresql | 7.2.4 |
| Postgresql | Postgresql | 7.2.5 |
| Postgresql | Postgresql | 7.2.6 |
| Postgresql | Postgresql | 7.2.7 |
| Postgresql | Postgresql | 7.2.8 |
| Postgresql | Postgresql | 7.3 |
| Postgresql | Postgresql | 7.3.1 |
| Postgresql | Postgresql | 7.3.2 |
| Postgresql | Postgresql | 7.3.3 |
| Postgresql | Postgresql | 7.3.4 |
| Postgresql | Postgresql | 7.3.5 |
| Postgresql | Postgresql | 7.3.6 |
| Postgresql | Postgresql | 7.3.7 |
| Postgresql | Postgresql | 7.3.8 |
| Postgresql | Postgresql | 7.3.9 |
| Postgresql | Postgresql | 7.3.10 |
| Postgresql | Postgresql | 7.3.11 |
| Postgresql | Postgresql | 7.3.12 |
| Postgresql | Postgresql | 7.3.13 |
Showing 50 of 92 affected configurations. See NVD for the full list.
References
- http://secunia.com/advisories/24033Vendor Advisory
- http://secunia.com/advisories/24033Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2007-0556?
How severe is CVE-2007-0556?
How do I fix CVE-2007-0556?
Are you affected by CVE-2007-0556?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
