# CVE-2020-13376: File upload in n/a

> Attackers can upload executable files via a crafted cookie to achieve OS command execution on SecurEnvoy SecurMail servers.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/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:** 7 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-33rv-x9gp-7cfh

## What is CVE-2020-13376?

CVE-2020-13376 is a critical vulnerability in n/a, published on 7 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SecurEnvoy SecurMail 9.3.503 allows attackers to upload executable files and achieve OS command execution via a crafted SecurEnvoyReply cookie.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Securenvoy Securmail.

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

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

## Is CVE-2020-13376 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-7702](https://insights.sbomify.com/CVE-2018-7702/): Missing authorization in n/a (critical 9.1)
- [CVE-2018-7705](https://insights.sbomify.com/CVE-2018-7705/): Path traversal in n/a (high 8.1)
- [CVE-2018-7701](https://insights.sbomify.com/CVE-2018-7701/): Multiple cross-site request forgery (CSRF) vulnerabilities in SecurEnvoy SecurMail before 9.2.501 allow remote attackers to hijack the authe (medium 6.5)
- [CVE-2018-7704](https://insights.sbomify.com/CVE-2018-7704/): Information disclosure in n/a (medium 6.5)
- [CVE-2018-7706](https://insights.sbomify.com/CVE-2018-7706/): Path traversal in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-13376 is a critical vulnerability in n/a, published on 7 Aug 2020. 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-2020-13376 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-13376/ (Markdown: https://insights.sbomify.com/CVE-2020-13376/index.md)
```

## Sources

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

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