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.
CVE-2005-0247 is a security vulnerability that . Impacting 1 product from postgresql organizations running these solutions should prioritize assessment and patching.
Originally identified in 2005, this vulnerability predates many modern security frameworks and practices. The vulnerability landscape of that era was characterized by different threat models and less mature defense mechanisms compared to contemporary standards.
2005-05-02T04:00:00.000
2025-04-03T01:03:51.193
Deferred
CVSSv2: 6.5 (MEDIUM)
AV:N/AC:L/Au:S/C:P/I:P/A:P
8.0
6.4
| Type | Vendor | Product | Version/Range | Vulnerable? |
|---|---|---|---|---|
| Application | postgresql | postgresql | 7.2 | Yes |
| Application | postgresql | postgresql | 7.2.1 | Yes |
| Application | postgresql | postgresql | 7.2.2 | Yes |
| Application | postgresql | postgresql | 7.2.3 | Yes |
| Application | postgresql | postgresql | 7.2.4 | Yes |
| Application | postgresql | postgresql | 7.2.5 | Yes |
| Application | postgresql | postgresql | 7.2.6 | Yes |
| Application | postgresql | postgresql | 7.2.7 | Yes |
| Application | postgresql | postgresql | 7.3 | Yes |
| Application | postgresql | postgresql | 7.3.1 | Yes |
| Application | postgresql | postgresql | 7.3.2 | Yes |
| Application | postgresql | postgresql | 7.3.3 | Yes |
| Application | postgresql | postgresql | 7.3.4 | Yes |
| Application | postgresql | postgresql | 7.3.5 | Yes |
| Application | postgresql | postgresql | 7.3.6 | Yes |
| Application | postgresql | postgresql | 7.3.7 | Yes |
| Application | postgresql | postgresql | 7.3.8 | Yes |
| Application | postgresql | postgresql | 7.3.9 | Yes |
| Application | postgresql | postgresql | 7.4 | Yes |
| Application | postgresql | postgresql | 7.4.1 | Yes |
| Application | postgresql | postgresql | 7.4.2 | Yes |
| Application | postgresql | postgresql | 7.4.3 | Yes |
| Application | postgresql | postgresql | 7.4.4 | Yes |
| Application | postgresql | postgresql | 7.4.5 | Yes |
| Application | postgresql | postgresql | 7.4.6 | Yes |
| Application | postgresql | postgresql | 7.4.7 | Yes |
| Application | postgresql | postgresql | 8.0.0 | Yes |
| Application | postgresql | postgresql | 8.0.1 | Yes |
SecUtils normalizes and enriches National Vulnerability Database (NVD) records by standardizing vendor and product identifiers, aggregating vulnerability metadata from both NVD and MITRE sources, and providing structured context for security teams. For postgresql's affected products, we extract Common Platform Enumeration (CPE) data, Common Weakness Enumeration (CWE) classifications, CVSS severity metrics, and reference data to enable rapid vulnerability prioritization and asset correlation. This record contains no exploit code, proof-of-concept instructions, or attack methodologies—only defensive intelligence necessary for patch management, risk assessment, and security operations.