# CVE-2002-1399: Integer overflow in n/a

> An integer overflow in PostgreSQL's cash_out function allows attackers to cause unexpected behavior via invalid input, requiring a version upgrade to fix.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-927w-qm35-gg94

## What is CVE-2002-1399?

CVE-2002-1399 is a critical vulnerability in Postgresql Postgresql, published on 8 Jan 2003. Any signed-in user can exploit it over the network, with no action from the victim.

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

## Which versions are affected by CVE-2002-1399?

It affects 1 product.


Products: Postgresql Postgresql.

## How do I fix CVE-2002-1399?

No fix has been published for CVE-2002-1399 yet. Limit exposure of the affected software until one is available.

## Is CVE-2002-1399 being exploited?

There is no known exploitation of CVE-2002-1399 in the wild and no public exploit code.

## Other vulnerabilities in Postgresql Postgresql

- [CVE-2013-1902](https://insights.sbomify.com/CVE-2013-1902/): Information disclosure in n/a (critical 10.0)
- [CVE-2013-1903](https://insights.sbomify.com/CVE-2013-1903/): Information disclosure in n/a (critical 10.0)
- [CVE-2007-3279](https://insights.sbomify.com/CVE-2007-3279/): Privilege escalation in n/a (critical 10.0)
- [CVE-2016-3065](https://insights.sbomify.com/CVE-2016-3065/): Information disclosure in n/a (critical 9.1)
- [CVE-2007-3280](https://insights.sbomify.com/CVE-2007-3280/): Code injection in n/a (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1399 and fix it if it is affected.

What it is: CVE-2002-1399 is a critical vulnerability in Postgresql Postgresql, published on 8 Jan 2003. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-1399 in the wild and no public exploit code.

Affected product: Postgresql Postgresql. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2002-1399/ (Markdown: https://insights.sbomify.com/CVE-2002-1399/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2002-1399
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2002-1399
- OSV: https://osv.dev/vulnerability/CVE-2002-1399

---
From sbomify Insights: https://insights.sbomify.com/CVE-2002-1399/
Summaries are generated and may contain mistakes; the official description above is the record.