# CVE-2003-0040: SQL injection in n/a

> Remote attackers can execute arbitrary SQL code via the username field in the Courier mail server's PostgreSQL authentication module.

- **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:** 1 Sep 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0040, DSA-247, GHSA-vrgp-v3rr-v9mg

## What is CVE-2003-0040?

CVE-2003-0040 is a high-severity SQL injection vulnerability in n/a, published on 1 Sep 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in the PostgreSQL auth module for courier 0.40 and earlier allows remote attackers to execute SQL code via the user name.

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

It affects 2 products.


Products: Double Precision Incorporated Courier Mta, Inter7 Courier-Imap.

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

Upgrade to a fixed version.

## Is CVE-2003-0040 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2659](https://insights.sbomify.com/CVE-2006-2659/): Denial of service in n/a (high 7.8)
- [CVE-2004-0224](https://insights.sbomify.com/CVE-2004-0224/): Memory corruption in n/a (high 7.5)
- [CVE-2002-0914](https://insights.sbomify.com/CVE-2002-0914/): Denial of service in n/a (medium 5.0)
- [CVE-2002-1311](https://insights.sbomify.com/CVE-2002-1311/): Information disclosure in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0040 and fix it if it is affected.

What it is: CVE-2003-0040 is a high-severity SQL injection vulnerability in n/a, published on 1 Sep 2004. 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-0040 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-2003-0040/ (Markdown: https://insights.sbomify.com/CVE-2003-0040/index.md)
```

## Sources

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

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