# CVE-2004-1129: SQL injection in n/a

> Remote attackers can inject SQL commands to delete mail metadata or contact addresses via the indexOfMail parameter in CMailServer.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-rm27-245w-3rmp

## What is CVE-2004-1129?

CVE-2004-1129 is a critical SQL injection vulnerability in n/a, published on 5 Dec 2004. It can be exploited over the network, with no action from the victim.

### Official description

SQL injection vulnerability in (1) fdelmail.asp, (2) addressc.asp, and possibly (3) postmail.asp and (4) fmvmail.asp in CMailServer 5.2 allow remote attackers to inject arbitrary SQL commands and delete mail metadata or e-mail addresses of contacts via the indexOfMail parameter.

## Which versions are affected by CVE-2004-1129?

It affects 1 product.


Products: Youngzsoft Cmailserver.

## How do I fix CVE-2004-1129?

No fix has been published for CVE-2004-1129 yet. Limit exposure of the affected software until one is available.

## Is CVE-2004-1129 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0280](https://insights.sbomify.com/CVE-2003-0280/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-6922](https://insights.sbomify.com/CVE-2008-6922/): Memory corruption in n/a (critical 9.3)
- [CVE-2002-0799](https://insights.sbomify.com/CVE-2002-0799/): Memory corruption in n/a (high 7.5)
- [CVE-2004-1130](https://insights.sbomify.com/CVE-2004-1130/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2007-1991](https://insights.sbomify.com/CVE-2007-1991/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-1129 and fix it if it is affected.

What it is: CVE-2004-1129 is a critical SQL injection vulnerability in n/a, published on 5 Dec 2004. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-1129 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-2004-1129/ (Markdown: https://insights.sbomify.com/CVE-2004-1129/index.md)
```

## Sources

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

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