CVE-2005-0247
Last modified
CVE-2005-0247 is a vulnerability of currently unknown severity. Multiple buffer overflows in gram.y for PostgreSQL 8.0.1 and earlier may allow attackers to execute arbitrary code via (1) a large number of variables in a SQL statement being handled by the read_sql_construct function, (2) a large number of INTO variables in a SELECT statement being handled by the make_select_stmt function, (3) a large number of arbitrary variables in a SELECT statement being handled by the make_select_stmt function, and (4) a large number of INTO variables in a FETCH statement being handled by the make_fetch_stmt function, a different set of vulnerabilities than CVE-2005-0245.. EPSS estimates a 3.51% chance of exploitation in the next 30 days.
Description
Multiple buffer overflows in gram.y for PostgreSQL 8.0.1 and earlier may allow attackers to execute arbitrary code via (1) a large number of variables in a SQL statement being handled by the read_sql_construct function, (2) a large number of INTO variables in a SELECT statement being handled by the make_select_stmt function, (3) a large number of arbitrary variables in a SELECT statement being handled by the make_select_stmt function, and (4) a large number of INTO variables in a FETCH statement being handled by the make_fetch_stmt function, a different set of vulnerabilities than CVE-2005-0245.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| 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.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.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 | 8.0.0 |
| Postgresql | Postgresql | 8.0.1 |
References
- http://www.gentoo.org/security/en/glsa/glsa-200502-19.xmlPatch, Vendor Advisory
- http://www.novell.com/linux/security/advisories/2005_27_postgresql.htmlPatch, Vendor Advisory
- http://www.redhat.com/support/errata/RHSA-2005-138.htmlPatch, Vendor Advisory
- http://www.redhat.com/support/errata/RHSA-2005-150.htmlPatch, Vendor Advisory
- http://www.gentoo.org/security/en/glsa/glsa-200502-19.xmlPatch, Vendor Advisory
- http://www.novell.com/linux/security/advisories/2005_27_postgresql.htmlPatch, Vendor Advisory
- http://www.redhat.com/support/errata/RHSA-2005-138.htmlPatch, Vendor Advisory
- http://www.redhat.com/support/errata/RHSA-2005-150.htmlPatch, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2005-0247?
How severe is CVE-2005-0247?
How do I fix CVE-2005-0247?
Are you affected by CVE-2005-0247?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
