PostgreSQLDatabase / datastore
CVE-2014-0065
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 · uneditedMultiple buffer overflows in PostgreSQL before 8.4.20, 9.0.x before 9.0.16, 9.1.x before 9.1.12, 9.2.x before 9.2.7, and 9.3.x before 9.3.3 allow remote authenticated users to have unspecified impact and attack vectors, a different vulnerability than CVE-2014-0063.
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 · moderate confidenceMultiple buffer overflow vulnerabilities in PostgreSQL versions prior to 8.4.20, 9.0.16, 9.1.12, 9.2.7, and 9.3.3 allow remote authenticated users to execute arbitrary code or cause denial of service through unspecified vectors.
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
<= 8.4.19= 8.4.1= 8.4.2= 8.4.3= 8.4.4= 8.4.5= 8.4.6= 8.4.7= 8.4.8= 8.4.9= 8.4.10= 8.4.11CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed PostgreSQL versionRun 'psql --version' or execute 'SELECT version();' as a database superuserAffected if The version is 8.4.19 or lower, 9.0.15 or lower, 9.1.11 or lower, 9.2.6 or lower, or 9.3.2 or lower (compare against the fixed versions: 8.4.20+, 9.0.16+, 9.1.12+, 9.2.7+, 9.3.3+)
-
Check if PostgreSQL accepts remote connectionsReview the PostgreSQL configuration file (postgresql.conf) for 'listen_addresses' setting and examine pg_hba.conf for any 'host' entries that allow remote IP addressesAffected if listen_addresses is set to '*' or includes specific remote IP addresses, AND pg_hba.conf contains host-based authentication rules for remote clients (this enables the remote attack vector)
-
Identify authentication method for remote connectionsExamine pg_hba.conf entries with type 'host' and review the authentication method specified (md5, password, trust, etc.)Affected if Remote authenticated users can connect (any method other than 'reject' for remote hosts means authenticated remote access is possible, which is required for this CVE to be exploitable)
You are affected if your PostgreSQL version is lower than 8.4.20, 9.0.16, 9.1.12, 9.2.7, or 9.3.3 AND remote authenticated access is enabled through pg_hba.conf and listen_addresses configuration.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade PostgreSQL to a patched version (8.4.20+, 9.0.16+, 9.1.12+, 9.2.7+, or 9.3.3+) and restrict network access to only trusted authenticated users.
Fix this in PostgreSQL
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0065 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sources- wiki.postgresql.org
- www.postgresql.org
- archives.neohapsis.com
- kb.juniper.net
- lists.opensuse.org
- lists.opensuse.org
- rhn.redhat.com
- rhn.redhat.com
- rhn.redhat.com
- rhn.redhat.com
- support.apple.com
- www.debian.org
- www.debian.org
- www.oracle.com
- www.securityfocus.com
- www.ubuntu.com
- support.apple.com
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-0065 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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