# CVE-2013-6810: File upload in n/a

> Remote attackers can execute arbitrary code by uploading an executable file via a servlet in Brocade Network Advisor.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-j9pg-xp47-h6c7

## What is CVE-2013-6810?

CVE-2013-6810 is a critical vulnerability in n/a, published on 12 Dec 2013. It can be exploited over the network, with no action from the victim.

### Official description

The server in Brocade Network Advisor before 12.1.0, as used in EMC Connectrix Manager Converged Network Edition (CMCNE), HP B-series SAN Network Advisor, and possibly other products, allows remote attackers to execute arbitrary code by using a servlet to upload an executable file.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2013-6810?

It affects 1 product.


Products: Emc Connectrix Manager.

## How do I fix CVE-2013-6810?

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

## Is CVE-2013-6810 being exploited?

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

Public exploit code:

- EMC CMCNE Inmservlets.war FileUploadController 11.2.1 - Remote Code Execution (Metasploit) (exploitdb)
- EMC CMCNE 11.2.1 - FileUploadController Remote Code Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-2276](https://insights.sbomify.com/CVE-2014-2276/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6810 and fix it if it is affected.

What it is: CVE-2013-6810 is a critical vulnerability in n/a, published on 12 Dec 2013. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-6810 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-2013-6810/ (Markdown: https://insights.sbomify.com/CVE-2013-6810/index.md)
```

## Sources

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

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