# CVE-2008-6922: Memory corruption in n/a

> Remote attackers can execute arbitrary code via stack-based buffer overflows in CMailServer ActiveX controls, requiring user interaction to trigger.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w655-3x88-v9g5

## What is CVE-2008-6922?

CVE-2008-6922 is a critical memory corruption vulnerability in n/a, published on 10 Aug 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Multiple stack-based buffer overflows in CMailCOM.dll in CMailServer 5.4.6 allow remote attackers to execute arbitrary code via a long argument to the (1) CreateUserPath, (2) Logout, (3) DeleteMailByUID, (4) MoveToInbox, (5) MoveToFolder, (6) DeleteMailEx, (7) GetMailDataEx, (8) SetReplySign, (9) SetForwardSign, and (10) SetReadSign methods, which are not properly handled by (a) the POP3 Class ActiveX control (CMailCom.POP3); or a long argument to the (11) AddAttach, (12) SetSubject, (13) SetBcc, (14) SetBody, (15) SetCc, (16) SetFrom, (17) SetTo, and (18) SetFromUID methods, which are not properly handled by the Class ActiveX control (CMailCOM.SMTP), as demonstrated via the indexOfMail parameter to mwmail.asp.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Youngzsoft Cmailserver.

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

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

## Is CVE-2008-6922 being exploited?

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

Public exploit code:

- Youngzsoft CMailServer 5.4.6 - 'CMailCOM.dll' Remote Overwrite (SEH) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-1129](https://insights.sbomify.com/CVE-2004-1129/): SQL injection in n/a (critical 10.0)
- [CVE-2003-0280](https://insights.sbomify.com/CVE-2003-0280/): Memory corruption in n/a (critical 10.0)
- [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-2008-6922 and fix it if it is affected.

What it is: CVE-2008-6922 is a critical memory corruption vulnerability in n/a, published on 10 Aug 2009. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-6922 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-2008-6922/ (Markdown: https://insights.sbomify.com/CVE-2008-6922/index.md)
```

## Sources

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

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