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

> Local attackers can cause denial of service or execute arbitrary code in PostgreSQL via a large negative argument in cash_words.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-83mr-c9w5-46g4

## What is CVE-2002-1397?

CVE-2002-1397 is a high-severity vulnerability in Postgresql Postgresql, published on 8 Jan 2003. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Vulnerability in the cash_words() function for PostgreSQL 7.2 and earlier allows local users to cause a denial of service and possibly execute arbitrary code via a large negative argument, possibly triggering an integer signedness error or buffer overflow.

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

It affects 1 product.


Products: Postgresql Postgresql.

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

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

## Is CVE-2002-1397 being exploited?

There is no known exploitation of CVE-2002-1397 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-2002-1399](https://insights.sbomify.com/CVE-2002-1399/): Integer overflow in n/a (critical 10.0)
- [CVE-2016-3065](https://insights.sbomify.com/CVE-2016-3065/): Information disclosure in n/a (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1397 is a high-severity vulnerability in Postgresql Postgresql, published on 8 Jan 2003. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-1397 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-1397/ (Markdown: https://insights.sbomify.com/CVE-2002-1397/index.md)
```

## Sources

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

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