# CVE-2019-13612: Security feature bypass in n/a

> MDaemon Email Server skips spam checks for large emails by default, allowing malicious messages to bypass security filters.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 16 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-gj3m-6662-4v94

## What is CVE-2019-13612?

CVE-2019-13612 is a high-severity vulnerability in n/a, published on 16 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MDaemon Email Server 19 through 20.0.1 skips SpamAssassin checks by default for e-mail messages larger than 2 MB (and limits checks to 10 MB even with special configuration), which is arguably inconsistent with currently popular message sizes. This might interfere with risk management for malicious e-mail, if a customer deploys a server with sufficient resources to scan large messages.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Altn Mdaemon Email Server.

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

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

## Is CVE-2019-13612 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-19497](https://insights.sbomify.com/CVE-2019-19497/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-13612 is a high-severity vulnerability in n/a, published on 16 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-13612 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-2019-13612/ (Markdown: https://insights.sbomify.com/CVE-2019-13612/index.md)
```

## Sources

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

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