CVE-2010-4015
Last modified
CVE-2010-4015 is a vulnerability of currently unknown severity. Buffer overflow in the gettoken function in contrib/intarray/_int_bool.c in the intarray array module in PostgreSQL 9.0.x before 9.0.3, 8.4.x before 8.4.7, 8.3.x before 8.3.14, and 8.2.x before 8.2.20 allows remote authenticated users to cause a denial of service (crash) and possibly execute arbitrary code via integers with a large number of digits to unspecified functions.. EPSS estimates a 4.62% chance of exploitation in the next 30 days.
Description
Buffer overflow in the gettoken function in contrib/intarray/_int_bool.c in the intarray array module in PostgreSQL 9.0.x before 9.0.3, 8.4.x before 8.4.7, 8.3.x before 8.3.14, and 8.2.x before 8.2.20 allows remote authenticated users to cause a denial of service (crash) and possibly execute arbitrary code via integers with a large number of digits to unspecified functions.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| 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 | 9.0 |
| Postgresql | Postgresql | 9.0.1 |
| Postgresql | Postgresql | 9.0.2 |
| 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.2 |
| Postgresql | Postgresql | 8.2.1 |
| Postgresql | Postgresql | 8.2.2 |
| Postgresql | Postgresql | 8.2.3 |
| Postgresql | Postgresql | 8.2.4 |
| Postgresql | Postgresql | 8.2.5 |
| Postgresql | Postgresql | 8.2.6 |
| Postgresql | Postgresql | 8.2.7 |
| Postgresql | Postgresql | 8.2.8 |
| Postgresql | Postgresql | 8.2.9 |
| Postgresql | Postgresql | 8.2.10 |
| Postgresql | Postgresql | 8.2.11 |
| Postgresql | Postgresql | 8.2.12 |
| Postgresql | Postgresql | 8.2.13 |
| Postgresql | Postgresql | 8.2.14 |
| Postgresql | Postgresql | 8.2.15 |
| Postgresql | Postgresql | 8.2.16 |
| Postgresql | Postgresql | 8.2.17 |
| Postgresql | Postgresql | 8.2.18 |
| Postgresql | Postgresql | 8.2.19 |
References
- http://secunia.com/advisories/43144Vendor Advisory
- http://www.vupen.com/english/advisories/2011/0262Vendor Advisory
- http://secunia.com/advisories/43144Vendor Advisory
- http://www.vupen.com/english/advisories/2011/0262Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2010-4015?
How severe is CVE-2010-4015?
How do I fix CVE-2010-4015?
Are you affected by CVE-2010-4015?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
