# CVE-2002-1401: Memory corruption in n/a

> Buffer overflows in PostgreSQL allow attackers to cause denial of service or execute arbitrary code via crafted inputs.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jan 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-xcqr-pm35-6p88

## What is CVE-2002-1401?

CVE-2002-1401 is a medium-severity memory corruption vulnerability in Postgresql Postgresql, published on 8 Jan 2003. It can be exploited over the network, with no action from the victim.

### Official description

Buffer overflows in (1) circle_poly, (2) path_encode and (3) path_add (also incorrectly identified as path_addr) for PostgreSQL 7.2.3 and earlier allow attackers to cause a denial of service and possibly execute arbitrary code, possibly as a result of an integer overflow.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Postgresql Postgresql.

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

Upgrade to a fixed version.

## Is CVE-2002-1401 being exploited?

There is no known exploitation of CVE-2002-1401 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-1401 and fix it if it is affected.

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

## Sources

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

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