# CVE-2012-2285: Auth bypass in n/a

> Remote attackers can gain GUI administrative access by sending a crafted file during authentication, compromising the EMC Cloud Tiering Appliance.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9cj5-qj56-q924

## What is CVE-2012-2285?

CVE-2012-2285 is a medium-severity authentication bypass vulnerability in n/a, published on 29 Aug 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

EMC Cloud Tiering Appliance (aka CTA, formerly FMA) 9.0 and earlier, and Cloud Tiering Appliance Virtual Edition (CTA/VE) 9.0 and earlier, allows remote attackers to obtain GUI administrative access by sending a crafted file during the authentication phase.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2012-2285?

It affects 2 products.


Products: Emc Cloud Tiering Appliance, Emc Cloud Tiering Appliance Virtual Edition.

## How do I fix CVE-2012-2285?

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

## Is CVE-2012-2285 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-0644](https://insights.sbomify.com/CVE-2014-0644/): XML external entity in n/a (high 7.8)
- [CVE-2014-0645](https://insights.sbomify.com/CVE-2014-0645/): Weak cryptography in n/a (medium 4.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2285 and fix it if it is affected.

What it is: CVE-2012-2285 is a medium-severity authentication bypass vulnerability in n/a, published on 29 Aug 2012. 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-2012-2285 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-2012-2285/ (Markdown: https://insights.sbomify.com/CVE-2012-2285/index.md)
```

## Sources

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

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