# CVE-2020-36519: Security feature bypass in n/a

> Administrators can spoof domains and bypass DMARC alignment via SPF by misusing the address rewrite feature in Mimecast Email Security.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2x44-42qx-w2fx

## What is CVE-2020-36519?

CVE-2020-36519 is a medium-severity vulnerability in n/a, published on 15 Mar 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Mimecast Email Security before 2020-01-10 allows any admin to spoof any domain, and pass DMARC alignment via SPF. This occurs through misuse of the address rewrite feature. (The domain being spoofed must be a customer in the Mimecast grid from which the spoofing occurs.)

## Which versions are affected by CVE-2020-36519?

It affects 1 product.


Products: Mimecast Email Security.

## How do I fix CVE-2020-36519?

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

## Is CVE-2020-36519 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36519 and fix it if it is affected.

What it is: CVE-2020-36519 is a medium-severity vulnerability in n/a, published on 15 Mar 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-36519 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-2020-36519/ (Markdown: https://insights.sbomify.com/CVE-2020-36519/index.md)
```

## Sources

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

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