# CVE-2012-2283: Missing authorization in n/a

> Authenticated users can read or modify data on arbitrary remote shares due to missing authorization checks in Iomega NAS firmware.

- **Severity:** Medium 5.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Aug 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-wgp4-h593-rgrw

## What is CVE-2012-2283?

CVE-2012-2283 is a medium-severity missing authorization vulnerability in n/a, published on 16 Aug 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Iomega Home Media Network Hard Drive with EMC Lifeline firmware before 2.104, Home Media Network Hard Drive Cloud Edition with EMC Lifeline firmware before 3.2.3.15290, iConnect with EMC Lifeline firmware before 2.5.26.18966, and StorCenter with EMC Lifeline firmware before 2.0.18.23122, 2.1.x before 2.1.42.18967, and 3.x before 3.2.3.15290 allow remote authenticated users to read or modify data on arbitrary remote shares via unspecified vectors.

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

It affects 4 products.


Products: Emc Lifeline, Iomega Home Media Network Hard Drive, Iomega Iconnect, Iomega Storcenter.

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

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

## Is CVE-2012-2283 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2283 is a medium-severity missing authorization vulnerability in n/a, published on 16 Aug 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-2283 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-2283/ (Markdown: https://insights.sbomify.com/CVE-2012-2283/index.md)
```

## Sources

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

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