# CVE-2003-0901: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a buffer overflow in PostgreSQL's to_ascii function, requiring immediate database upgrades.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Oct 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DSA-397, GHSA-8584-8hj6-m5v3

## What is CVE-2003-0901?

CVE-2003-0901 is a high-severity memory corruption vulnerability in Postgresql Postgresql, published on 30 Oct 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in to_ascii for PostgreSQL 7.2.x, and 7.3.x before 7.3.4, allows remote attackers to execute arbitrary code.

## Which versions are affected by CVE-2003-0901?

It affects 1 product.


Products: Postgresql Postgresql.

## How do I fix CVE-2003-0901?

Upgrade to a fixed version.

## Is CVE-2003-0901 being exploited?

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

What it is: CVE-2003-0901 is a high-severity memory corruption vulnerability in Postgresql Postgresql, published on 30 Oct 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0901 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-2003-0901/ (Markdown: https://insights.sbomify.com/CVE-2003-0901/index.md)
```

## Sources

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

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