Libdbd Pg PerlApplication · Debian
CVE-2009-1341
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 · uneditedMemory leak in the dequote_bytea function in quote.c in the DBD::Pg (aka DBD-Pg or libdbd-pg-perl) module before 2.0.0 for Perl allows context-dependent attackers to cause a denial of service (memory consumption) by fetching data with BYTEA columns.
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 confidenceMemory leak in the dequote_bytea function in quote.c in DBD::Pg (Perl PostgreSQL driver) before version 2.0.0. When fetching data containing BYTEA (binary) columns, allocated memory is not properly freed, leading to progressive memory consumption and potential denial of service.
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
Libdbd Pg PerlApplication
<= 1.4.9= 0.1= 0.2= 0.3= 0.4= 0.5= 0.51= 0.52= 0.61= 0.62= 0.63= 0.64CVSS 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
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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.
-
Check if DBD::Pg is installedRun `perl -MDBD::Pg -e 'print $DBD::Pg::VERSION'` or `perl -e 'use DBD::Pg; print $DBD::Pg::VERSION'`. If the module is not installed, the command will fail.Affected if DBD::Pg is not installed or the command returns a version number.
-
Compare installed version to affected rangeExamine the version number from step 1. Versions before 2.0.0 (such as 1.4.9 or any 0.x version like 0.51, 0.62, etc.) are affected.Affected if The installed version is less than 2.0.0, including all 0.x versions and 1.x versions up to 1.4.9.
-
Identify if BYTEA column fetching occursReview application code or database queries for SELECT statements that retrieve BYTEA (binary) columns from PostgreSQL tables. Check for usage patterns like `$sth->fetchrow_array` or `$sth->fetch` on tables containing BYTEA fields.Affected if The environment fetches BYTEA data from PostgreSQL using DBD::Pg. The vulnerability only triggers when binary column data is retrieved.
-
Monitor for progressive memory growthObserve the Perl process memory usage over time while the application fetches BYTEA data from PostgreSQL. On systems with affected DBD::Pg versions, memory usage will increase with each fetch operation involving binary data.Affected if Memory consumption grows progressively during BYTEA column fetches, indicating the unreleased memory allocation from the dequote_bytea function.
You are affected if DBD::Pg version is below 2.0.0 AND your application fetches BYTEA (binary) columns from PostgreSQL, resulting in progressive memory growth in the process.
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 DBD::Pg module to version 2.0.0 or later to obtain the patched version of dequote_bytea that properly manages memory allocation and deallocation.
Fix this in Libdbd Pg Perl
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-1341 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2009-1341 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