How severe is CVE-2002-1399?

CVE-2002-1399 has a CVSS 2.0 base score of 10.0, rated critical severity.

Is CVE-2002-1399 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (76th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2002-1399?

CVE-2002-1399 primarily affects Postgresql. In total, 9 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2002-1399?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2002-1399 published?

CVE-2002-1399 was published on 2003-01-17 and last updated on 2026-06-16.

CVE-2002-1399

CVE-2002-1399 is a critical-severity vulnerability in Postgresql with a CVSS 2.0 base score of 10.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Critical (CVSS 2.0 base score 10.0)
EPSS exploit prediction: 2% (76th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Postgresql
Published: 2003-01-17
Last modified: 2026-06-16

Description

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

Frequently asked questions

What is CVE-2002-1399?: 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).
How severe is CVE-2002-1399?: CVE-2002-1399 has a CVSS 2.0 base score of 10.0, rated critical severity.
Is CVE-2002-1399 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (76th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2002-1399?: CVE-2002-1399 primarily affects Postgresql. In total, 9 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2002-1399?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2002-1399 published?: CVE-2002-1399 was published on 2003-01-17 and last updated on 2026-06-16.

References

Affected products (9)

cpe:2.3:a:postgresql:postgresql:6.3.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:6.5.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:7.0.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:7.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:7.1.1:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:7.1.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:7.1.3:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:7.2:*:*:*:*:*:*:*
cpe:2.3:a:postgresql:postgresql:7.2.1:*:*:*:*:*:*:*