# CVE-2005-0247: Memory corruption in n/a

> Buffer overflows in PostgreSQL parser allow attackers to execute arbitrary code via crafted SQL statements.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-ggh8-6p3g-2rw7

## What is CVE-2005-0247?

CVE-2005-0247 is a medium-severity memory corruption vulnerability in Postgresql Postgresql, published on 8 Feb 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple buffer overflows in gram.y for PostgreSQL 8.0.1 and earlier may allow attackers to execute arbitrary code via (1) a large number of variables in a SQL statement being handled by the read_sql_construct function, (2) a large number of INTO variables in a SELECT statement being handled by the make_select_stmt function, (3) a large number of arbitrary variables in a SELECT statement being handled by the make_select_stmt function, and (4) a large number of INTO variables in a FETCH statement being handled by the make_fetch_stmt function, a different set of vulnerabilities than CVE-2005-0245.

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

## Which versions are affected by CVE-2005-0247?

It affects 1 product.


Products: Postgresql Postgresql.

## How do I fix CVE-2005-0247?

Upgrade to a fixed version.

## Is CVE-2005-0247 being exploited?

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

What it is: CVE-2005-0247 is a medium-severity memory corruption vulnerability in Postgresql Postgresql, published on 8 Feb 2005. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-0247 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-2005-0247/ (Markdown: https://insights.sbomify.com/CVE-2005-0247/index.md)
```

## Sources

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

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