CVE-2002-1399

What it is

Unknown 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).

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

1.8% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2003-01-17 05:00 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 21:59 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.8% in the next 30 days (EPSS).
• Severity: 10.0 HIGH (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2003-01-17 05:00 UTC

Last modified

2026-06-16 21:59 UTC

Exploit probability

1.8% · EPSS, next 30 days

Record status

Modified

Affected

• PostgreSQL 6.3.2
• PostgreSQL 6.5.3
• PostgreSQL 7.0.3
• PostgreSQL 7.1
• PostgreSQL 7.1.1
• PostgreSQL 7.1.2
• PostgreSQL 7.1.3
• PostgreSQL 7.2

Attack profile CVSS 2.0 · 10.0

Attack vector

Network

Complexity

Low

Authentication

None

Confidentiality

Complete

Integrity

Complete

Availability

Complete

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2002-1399.md and follow it. Check whether this project is affected by CVE-2002-1399. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge