# CVE-2008-2380: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands in Courier-Authlib when using non-Latin locale Postgres databases, potentially compromising data integrity and confidentiality.

- **Severity:** Medium 5.1 (`AV:N/AC:H/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:** 22 Dec 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-2380, DTSA-180-1, GHSA-p4v2-gpr7-p49q

## What is CVE-2008-2380?

CVE-2008-2380 is a medium-severity SQL injection vulnerability in n/a, published on 22 Dec 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in authpgsqllib.c in Courier-Authlib before 0.62.0, when a non-Latin locale Postgres database is used, allows remote attackers to execute arbitrary SQL commands via query parameters containing apostrophes.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2008-2380?

It affects 1 product.


Products: Courier-Mta Courtier-Authlib.

## How do I fix CVE-2008-2380?

Upgrade to a fixed version.

## Is CVE-2008-2380 being exploited?

There is no known exploitation of CVE-2008-2380 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2008-2667](https://insights.sbomify.com/CVE-2008-2667/): SQL injection in n/a (medium 5.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-2380 and fix it if it is affected.

What it is: CVE-2008-2380 is a medium-severity SQL injection vulnerability in n/a, published on 22 Dec 2008. 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-2008-2380 in the wild and no public exploit code.

Affected product: n/a. 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-2008-2380/ (Markdown: https://insights.sbomify.com/CVE-2008-2380/index.md)
```

## Sources

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

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