# CVE-2014-2276: Information disclosure in n/a

> Remote attackers can obtain sensitive information by importing a crafted firmware file into the EMC Connectrix Manager repository.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3w68-p3xg-cp6h

## What is CVE-2014-2276?

CVE-2014-2276 is a medium-severity vulnerability in n/a, published on 21 Mar 2014. It can be exploited over the network, with no action from the victim.

### Official description

The FileUploadController servlet in EMC Connectrix Manager Converged Network Edition (CMCNE) before 12.1.5 does not properly restrict additions to the Connectrix Manager repository, which allows remote attackers to obtain sensitive information by importing a crafted firmware file.

Weakness: CWE-264

## Which versions are affected by CVE-2014-2276?

It affects 1 product.


Products: Emc Connectrix Manager.

## How do I fix CVE-2014-2276?

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

## Is CVE-2014-2276 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-6810](https://insights.sbomify.com/CVE-2013-6810/): File upload in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2276 and fix it if it is affected.

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

## Sources

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

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