# CVE-2019-7214: Deserialization in n/a

> Unauthenticated attackers can execute arbitrary commands on SmarterMail servers if port 17001 is remotely accessible, requiring a patch to secure the default configuration.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-7mgm-6cgr-gh26

## What is CVE-2019-7214?

CVE-2019-7214 is a critical unsafe deserialization vulnerability in n/a, published on 24 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SmarterTools SmarterMail 16.x before build 6985 allows deserialization of untrusted data. An unauthenticated attacker could run commands on the server when port 17001 was remotely accessible. This port is not accessible remotely by default after applying the Build 6985 patch.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2019-7214?

It affects 1 product.


Products: Smartertools Smartermail.

## How do I fix CVE-2019-7214?

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

## Is CVE-2019-7214 being exploited?

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

Public exploit code:

- Python3 Rewrite of SmarterMail < Build 6985 Remote Code Execution found by 1F98D (CVE-2019-7214) POC (github_poc): https://github.com/Drew-Alleman/CVE-2019-7214
- Collection of PoCs created for SmarterMail < Build 6985 RCE (github_poc): https://github.com/devzspy/CVE-2019-7214
- https://github.com/andyfeili/-CVE-2019-7214 (github_poc): https://github.com/andyfeili/-CVE-2019-7214
- SmarterTools SmarterMail less than build 6985 - .NET Deserialization Remote Code Execution (metasploit)
- SmarterMail Build 6985 - Remote Code Execution (exploitdb)
- For CTF use only (the CVE-2019-7214 also resolves the host from /etc/hosts) (github_poc): https://github.com/ElusiveHacker/CVE-2019-7214

## Other vulnerabilities in n/a

- [CVE-2025-52691](https://insights.sbomify.com/CVE-2025-52691/): SmarterTools SmarterMail Unrestricted Upload of File with Dangerous Type (critical 10.0, exploited in the wild)
- [CVE-2026-24423](https://insights.sbomify.com/CVE-2026-24423/): SmarterTools SmarterMail Missing Authentication for Critical Function (critical 9.3, exploited in the wild)
- [CVE-2026-23760](https://insights.sbomify.com/CVE-2026-23760/): SmarterTools SmarterMail Authentication Bypass Using an Alternate Path or Channel (critical 9.3, exploited in the wild)
- [CVE-2021-32234](https://insights.sbomify.com/CVE-2021-32234/): Code injection in n/a (critical 9.8)
- [CVE-2026-7807](https://insights.sbomify.com/CVE-2026-7807/): SmarterTools SmarterMail < Build 9560 Server Local File Inclusion via the /api/v1/report/summary/{type} API (high 8.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-7214 and fix it if it is affected.

What it is: CVE-2019-7214 is a critical unsafe deserialization vulnerability in n/a, published on 24 Apr 2019. 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-2019-7214 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-2019-7214/ (Markdown: https://insights.sbomify.com/CVE-2019-7214/index.md)
```

## Sources

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

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