PostgreSQLDatabase / datastore
CVE-2002-1399
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 · uneditedUnknown vulnerability in cash_out and possibly other functions in PostgreSQL 7.2.1 and earlier, and possibly later versions before 7.2.3, with unknown impact, based on an invalid integer input which is processed as a different data type, as demonstrated using cash_out(2).
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 confidenceType confusion vulnerability in PostgreSQL 7.2.x where the cash_out function (and possibly others) improperly handles invalid integer input, processing it as a different data type. This could allow attackers to trigger unintended behavior or potentially execute arbitrary code through specially crafted input.
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
= 6.3.2= 6.5.3= 7.0.3= 7.1= 7.1.1= 7.1.2= 7.1.3= 7.2= 7.2.1CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed PostgreSQL versionRun 'psql --version' or 'SELECT version();' query from psql client to get the exact PostgreSQL version numberAffected if Version matches 6.3.2, 6.5.3, 7.0.3, 7.1, 7.1.1, 7.1.2, 7.1.3, 7.2, or 7.2.1
-
Verify cash_out function existsConnect to the database and run 'SELECT proname FROM pg_proc WHERE proname = 'cash_out';' to check if the function is definedAffected if The cash_out function exists in the database schema
-
Check for type conversion behaviorTest with invalid integer input to the cash_out function (e.g., passing non-numeric strings or special characters) to observe if type confusion occursAffected if Invalid input is processed without proper type validation errors or triggers unexpected behavior
-
Confirm PostgreSQL is accepting user input to cash_outReview database permissions and function definitions using '\df cash_out' in psql to see if the function is exposed to untrusted usersAffected if Untrusted users can call the cash_out function with arbitrary input
The environment is affected if the installed PostgreSQL version is one of the listed affected versions AND the cash_out function is accessible to users who could supply malicious input.
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.
dbcve · scopedUpgrade PostgreSQL to version 7.2.3 or later; ideally migrate to a currently supported PostgreSQL version (13+) as 7.2.x is obsolete and no longer receives security patches.
PostgreSQL 7.2.3 or later (or migrate to a currently supported PostgreSQL release such as 14/15/16)
- Upgrade PostgreSQL to version 7.2.3 or later to resolve the type confusion vulnerability in cash_out and related functions.
- If running PostgreSQL 6.x or 7.0.x/7.1.x, plan a migration path to a currently supported PostgreSQL release (modern supported versions include PostgreSQL 13, 14, 15, or 16).
- Before upgrading, back up all databases using pg_dumpall.
- Test the upgrade in a staging environment before deploying to production.
- After upgrading, verify that applications using cash_out() and similar functions work correctly with proper integer inputs.
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in PostgreSQL
Scoped from the published advisory
- Consultation8.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $22,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1399 — 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-2002-1399 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