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

> Remote attackers can execute arbitrary code via stack-based buffer overflows in SL Mail Pro DLLs.

- **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:** 18 Mar 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-mmrr-cxj4-wjr9

## What is CVE-2004-0357?

CVE-2004-0357 is a critical memory corruption vulnerability in n/a, published on 18 Mar 2004. It can be exploited over the network, with no action from the victim.

### Official description

Stack-based buffer overflows in SL Mail Pro 2.0.9 allow remote attackers to execute arbitrary code via (1) user.dll, (2) loadpageadmin.dll or (3) loadpageuser.dll.

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

It affects 1 product.


Products: Seattle Lab Software Slmail Pro.

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

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

## Is CVE-2004-0357 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-1690](https://insights.sbomify.com/CVE-2008-1690/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0356](https://insights.sbomify.com/CVE-2004-0356/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-1689](https://insights.sbomify.com/CVE-2008-1689/): Denial of service in n/a (medium 5.0)
- [CVE-2008-1691](https://insights.sbomify.com/CVE-2008-1691/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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