# CVE-2010-20119: CommuniCrypt Mail <= 1.16 ANSMTP/AOSMTP ActiveX Control Buffer Overflow

> A stack-based buffer overflow in CommuniCrypt Mail's ActiveX controls allows attackers to execute arbitrary code via crafted input.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 21 Aug 2025
- **Updated:** 15 May 2026
- **Also known as:** GHSA-mcx6-3vph-g228

## What is CVE-2010-20119?

CVE-2010-20119 is a high-severity memory corruption vulnerability in CommuniCrypt Mail, published on 21 Aug 2025. 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

CommuniCrypt Mail versions up to and including 1.16 contains a stack-based buffer overflow vulnerability in its ANSMTP.dll  and AOSMTP.dll  ActiveX controls, specifically within the AddAttachments() method. This method fails to properly validate the length of input strings, allowing data to exceed the bounds of a fixed-size stack buffer. When invoked with an overly long string, the control can corrupt adjacent memory structures, including exception handlers, leading to potential control flow disruption.

Weakness: CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2010-20119?


## How do I fix CVE-2010-20119?

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

## Is CVE-2010-20119 being exploited?

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

Public exploit code:

- CommuniCrypt Mail 1.16 SMTP ActiveX Stack Buffer Overflow (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-20119 and fix it if it is affected.

What it is: CVE-2010-20119 is a high-severity memory corruption vulnerability in CommuniCrypt Mail, published on 21 Aug 2025. 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-2010-20119 exists.

Affected product: CommuniCrypt Mail. 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-2010-20119/ (Markdown: https://insights.sbomify.com/CVE-2010-20119/index.md)
```

## Sources

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

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