# CVE-2004-2003: Memory corruption in n/a

> Remote attackers can execute arbitrary code via a buffer overflow in the SSLway filter when processing certificates with long subject or issuer names.

- **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:** No
- **Published:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-frvx-gppg-h8rp

## What is CVE-2004-2003?

CVE-2004-2003 is a high-severity memory corruption vulnerability in n/a, published on 10 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the ssl_prcert function in the SSLway filter (sslway.c) for DeleGate 8.9.2 and earlier allows remote attackers to execute arbitrary code via a certificate with a long (1) subject or (2) issuer name field.

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

It affects 1 product.


Products: Delegate Delegate.

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

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

## Is CVE-2004-2003 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-2003 exists.

Public exploit code:

- DeleGate 7.8.x/8.x - SSLway Filter Remote Stack Buffer Overflow (PoC) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2015-7556](https://insights.sbomify.com/CVE-2015-7556/): Privilege escalation in DeleGate (high 7.8)
- [CVE-2002-1781](https://insights.sbomify.com/CVE-2002-1781/): Memory corruption in n/a (high 7.5)
- [CVE-2005-0861](https://insights.sbomify.com/CVE-2005-0861/): Memory corruption in n/a (high 7.5)
- [CVE-2001-1202](https://insights.sbomify.com/CVE-2001-1202/): Cross-site scripting in n/a (high 7.5)
- [CVE-2005-0036](https://insights.sbomify.com/CVE-2005-0036/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-2003 is a high-severity memory corruption vulnerability in n/a, published on 10 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-2003 exists.

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-2003/ (Markdown: https://insights.sbomify.com/CVE-2004-2003/index.md)
```

## Sources

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

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