# CVE-2006-2313: SQL injection in n/a

> Attackers can bypass SQL injection protections in applications using PostgreSQL by exploiting invalid multibyte character encodings, leading to unauthorized data access or modification.

- **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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-ggvw-qxcq-2xgj

## What is CVE-2006-2313?

CVE-2006-2313 is a high-severity SQL injection vulnerability in Postgresql Postgresql, published on 24 May 2006. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PostgreSQL 8.1.x before 8.1.4, 8.0.x before 8.0.8, 7.4.x before 7.4.13, 7.3.x before 7.3.15, and earlier versions allows context-dependent attackers to bypass SQL injection protection methods in applications via invalid encodings of multibyte characters, aka one variant of "Encoding-Based SQL Injection."

## Which versions are affected by CVE-2006-2313?

It affects 1 product.


Products: Postgresql Postgresql.

## How do I fix CVE-2006-2313?

Upgrade to a fixed version.

## Is CVE-2006-2313 being exploited?

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

What it is: CVE-2006-2313 is a high-severity SQL injection vulnerability in Postgresql Postgresql, published on 24 May 2006. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-2313 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-2006-2313/ (Markdown: https://insights.sbomify.com/CVE-2006-2313/index.md)
```

## Sources

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

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