Vulnerability Monitor

The vendors, products, and vulnerabilities you care about

CVE-2007-0556

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.

Security Impact Summary

CVE-2007-0556 is a security vulnerability that . Impacting 1 product from postgresql organizations running these solutions should prioritize assessment and patching.

Historical Context

Originally identified in 2007, 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.

Published

2007-02-06T01:28:00.000

Last Modified

2025-04-09T00:30:58.490

Status

Deferred

Source

[email protected]

Severity

CVSSv2: 6.6 (MEDIUM)

CVSSv2 Vector

AV:N/AC:H/Au:S/C:C/I:N/A:C

  • Access Vector: NETWORK
  • Access Complexity: HIGH
  • Authentication: SINGLE
  • Confidentiality Impact: COMPLETE
  • Integrity Impact: NONE
  • Availability Impact: COMPLETE
Exploitability Score

3.9

Impact Score

9.2

Weaknesses
  • Type: Primary
    NVD-CWE-Other
Affected Vendors & Products
Type Vendor Product Version/Range Vulnerable?
Application postgresql postgresql 1.0 Yes
Application postgresql postgresql 1.01 Yes
Application postgresql postgresql 1.02 Yes
Application postgresql postgresql 1.09 Yes
Application postgresql postgresql 6.0 Yes
Application postgresql postgresql 6.1 Yes
Application postgresql postgresql 6.1.1 Yes
Application postgresql postgresql 6.2 Yes
Application postgresql postgresql 6.2.1 Yes
Application postgresql postgresql 6.3 Yes
Application postgresql postgresql 6.3.1 Yes
Application postgresql postgresql 6.3.2 Yes
Application postgresql postgresql 6.4 Yes
Application postgresql postgresql 6.4.1 Yes
Application postgresql postgresql 6.4.2 Yes
Application postgresql postgresql 6.5 Yes
Application postgresql postgresql 6.5.1 Yes
Application postgresql postgresql 6.5.2 Yes
Application postgresql postgresql 6.5.3 Yes
Application postgresql postgresql 7.0 Yes
Application postgresql postgresql 7.0.1 Yes
Application postgresql postgresql 7.0.2 Yes
Application postgresql postgresql 7.0.3 Yes
Application postgresql postgresql 7.1 Yes
Application postgresql postgresql 7.1.1 Yes
Application postgresql postgresql 7.1.2 Yes
Application postgresql postgresql 7.1.3 Yes
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.2.8 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.3.10 Yes
Application postgresql postgresql 7.3.11 Yes
Application postgresql postgresql 7.3.12 Yes
Application postgresql postgresql 7.3.13 Yes
Application postgresql postgresql 7.3.14 Yes
Application postgresql postgresql 7.3.15 Yes
Application postgresql postgresql 7.3.16 Yes
Application postgresql postgresql 7.3.17 Yes
Application postgresql postgresql 7.3.18 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 7.4.8 Yes
Application postgresql postgresql 7.4.9 Yes
Application postgresql postgresql 7.4.10 Yes
Application postgresql postgresql 7.4.11 Yes
Application postgresql postgresql 7.4.12 Yes
Application postgresql postgresql 7.4.13 Yes
Application postgresql postgresql 7.4.14 Yes
Application postgresql postgresql 7.4.15 Yes
Application postgresql postgresql 7.4.16 Yes
Application postgresql postgresql 8.0 Yes
Application postgresql postgresql 8.0.1 Yes
Application postgresql postgresql 8.0.2 Yes
Application postgresql postgresql 8.0.3 Yes
Application postgresql postgresql 8.0.4 Yes
Application postgresql postgresql 8.0.5 Yes
Application postgresql postgresql 8.0.6 Yes
Application postgresql postgresql 8.0.7 Yes
Application postgresql postgresql 8.0.8 Yes
Application postgresql postgresql 8.0.9 Yes
Application postgresql postgresql 8.0.10 Yes
Application postgresql postgresql 8.1 Yes
Application postgresql postgresql 8.1.1 Yes
Application postgresql postgresql 8.1.2 Yes
Application postgresql postgresql 8.1.3 Yes
Application postgresql postgresql 8.1.4 Yes
Application postgresql postgresql 8.1.5 Yes
Application postgresql postgresql 8.1.6 Yes
Application postgresql postgresql 8.2 Yes
Application postgresql postgresql 8.2.1 Yes
References

How SecUtils Interprets This CVE

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.