CVE-2006-5540
Last modified
CVE-2006-5540 is a vulnerability of currently unknown severity. backend/parser/analyze.c in PostgreSQL 8.1.x before 8.1.5 allows remote authenticated users to cause a denial of service (daemon crash) via certain aggregate functions in an UPDATE statement, which are not properly handled during a "MIN/MAX index optimization.". EPSS estimates a 1.88% chance of exploitation in the next 30 days.
Description
backend/parser/analyze.c in PostgreSQL 8.1.x before 8.1.5 allows remote authenticated users to cause a denial of service (daemon crash) via certain aggregate functions in an UPDATE statement, which are not properly handled during a "MIN/MAX index optimization."
Metrics
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Postgresql | Postgresql | 6.3.2 |
| Postgresql | Postgresql | 6.5.3 |
| 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.7 |
| 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.6 |
| 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 |
| Postgresql | Postgresql | 7.3.14 |
| Postgresql | Postgresql | 7.3.15 |
| Postgresql | Postgresql | 7.4 |
| Postgresql | Postgresql | 7.4.1 |
| Postgresql | Postgresql | 7.4.2 |
| Postgresql | Postgresql | 7.4.3 |
| Postgresql | Postgresql | 7.4.4 |
| Postgresql | Postgresql | 7.4.5 |
| Postgresql | Postgresql | 7.4.6 |
| Postgresql | Postgresql | 7.4.7 |
| Postgresql | Postgresql | 7.4.8 |
| Postgresql | Postgresql | 7.4.9 |
| Postgresql | Postgresql | 7.4.10 |
| Postgresql | Postgresql | 7.4.11 |
| Postgresql | Postgresql | 7.4.12 |
| Postgresql | Postgresql | 7.4.13 |
| Postgresql | Postgresql | 8.0 |
| Postgresql | Postgresql | 8.0.1 |
| Postgresql | Postgresql | 8.0.2 |
| Postgresql | Postgresql | 8.0.3 |
| Postgresql | Postgresql | 8.0.4 |
| Postgresql | Postgresql | 8.0.5 |
| Postgresql | Postgresql | 8.0.6 |
| Postgresql | Postgresql | 8.0.7 |
Showing 50 of 56 affected configurations. See NVD for the full list.
References
- http://secunia.com/advisories/22562Patch, Vendor Advisory
- http://secunia.com/advisories/22584Patch, Vendor Advisory
- http://secunia.com/advisories/22562Patch, Vendor Advisory
- http://secunia.com/advisories/22584Patch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2006-5540?
How severe is CVE-2006-5540?
How do I fix CVE-2006-5540?
Are you affected by CVE-2006-5540?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST