dbcve.org
PostgreSQLDatabase / datastore

CVE-2010-4015

MEDIUM · 6.5 CVSS v2.0 Published 2011-02-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
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
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.

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

Buffer overflow in the gettoken function in PostgreSQL's intarray module (_int_bool.c) allows remote authenticated users to crash the database or potentially execute arbitrary code by passing integers with an excessively large number of digits.

MitigationUpgrade PostgreSQL to version 9.0.3, 8.4.7, 8.3.14, 8.2.20 or later to patch the vulnerability. If the intarray module is not required, disable or remove it to reduce attack surface.

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:= 8.3= 8.3.1= 8.3.2= 8.3.3= 8.3.4= 8.3.5= 8.3.6= 8.3.7= 8.3.8= 8.3.9= 8.3.10= 8.3.11

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
Partial
Integrity
Partial
Availability
Partial

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

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. Identify installed PostgreSQL version
    Run `psql --version` or `SELECT version();` to obtain the PostgreSQL server version number
    Affected if The version is 8.3.0 through 8.3.11 inclusive (the affected range)
  2. Locate the intarray module
    Check for the presence of the intarray module files (typically _int.so or _int.bundle in the lib directory) or query `SELECT * FROM pg_available_extensions WHERE name = 'intarray';`
    Affected if The intarray module files exist on the system
  3. Check if intarray extension is created
    Query `SELECT * FROM pg_extension WHERE extname = 'intarray';` in each database
    Affected if The intarray extension is installed in any database (making the vulnerable code loadable)
  4. Verify the intarray module is in use
    Review database schemas for objects (operators, functions) owned by the intarray extension, or check for usage of the ~ (match) operator on integer arrays which relies on intarray
    Affected if Any tables or queries utilize intarray functionality

You are affected if you run PostgreSQL 8.3.0-8.3.11 AND have the intarray extension created in any database, as the buffer overflow in the gettoken function becomes exploitable only when the vulnerable module code is loaded.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade PostgreSQL to version 9.0.3, 8.4.7, 8.3.14, 8.2.20 or later to patch the vulnerability. If the intarray module is not required, disable or remove it to reduce attack surface.

Fix this in PostgreSQL Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-4015 — 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-2010-4015 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