dbcve.org
PostgreSQLDatabase / datastore

CVE-2007-0555

HIGH · 8.5 CVSS v2.0 Published 2007-02-06
Fix available
A fix is available. Upgrade to 7.3.18 / 7.4.16 or later.
See remediation →
91/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
PostgreSQL 7.3 before 7.3.13, 7.4 before 7.4.16, 8.0 before 8.0.11, 8.1 before 8.1.7, and 8.2 before 8.2.2 allows attackers to disable certain checks for the data types of SQL function arguments, which allows remote authenticated users to cause a denial of service (server crash) and possibly access database content.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

PostgreSQL versions 7.3-8.2 contain a vulnerability where type checking for SQL function arguments can be bypassed, allowing authenticated remote users to crash the server (DoS) or potentially access unauthorized database content.

MitigationUpgrade PostgreSQL to version 7.3.13, 7.4.16, 8.0.11, 8.1.7, 8.2.2 or later. If upgrading to a supported major version is not feasible, apply the vendor-supplied patches to the affected versions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PostgreSQLDatabase / datastore
Affected:>= 7.3, < 7.3.18>= 7.4, < 7.4.16>= 8.0, < 8.0.11>= 8.1, < 8.1.7>= 8.2, < 8.2.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
Single
Confidentiality
Complete
Integrity
None
Availability
Complete

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check PostgreSQL server version
    Run `psql --version` or `pg_config --version` from the command line, or connect to the database and run `SELECT version();`
    Affected if The version output shows a version >= 7.3 but less than 7.3.18, OR >= 7.4 but less than 7.4.16, OR >= 8.0 but less than 8.0.11, OR >= 8.1 but less than 8.1.7, OR >= 8.2 but less than 8.2.2
  2. Confirm database server is accessible
    Verify you can connect to the PostgreSQL instance using psql or any client with valid credentials
    Affected if The server is running and accepts connections (the vulnerability requires an authenticated session to exploit)
  3. Identify if custom SQL functions exist
    Query the pg_proc catalog: `SELECT proname, pronargs FROM pg_proc WHERE pronargs > 0;` or review application SQL code for user-defined functions
    Affected if The database uses custom SQL functions with arguments (the vulnerability exploits argument type checking in SQL functions)

You are affected if the running PostgreSQL version falls within any of the vulnerable ranges (7.3 to 7.3.17, 7.4 to 7.4.15, 8.0 to 8.0.10, 8.1 to 8.1.6, or 8.2 to 8.2.1) and the database accepts authenticated connections from remote or local users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 7.3.18 / 7.4.16 / 8.0.11 or later
Fixed in 7.3.187.4.168.0.11
Interim mitigation

Upgrade PostgreSQL to version 7.3.13, 7.4.16, 8.0.11, 8.1.7, 8.2.2 or later. If upgrading to a supported major version is not feasible, apply the vendor-supplied patches to the affected versions.

Fix this in PostgreSQL Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-0555 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-0555 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data