# CVE-2012-2163: Code injection in n/a

> Remote authenticated administrators can execute arbitrary Linux commands on IBM SONAS storage systems via CLI or GUI.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f598-w9pf-6r29

## What is CVE-2012-2163?

CVE-2012-2163 is a critical code injection vulnerability in n/a, published on 30 Jul 2012. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

IBM Scale Out Network Attached Storage (SONAS) 1.1 through 1.3.1 allows remote authenticated administrators to execute arbitrary Linux commands via the (1) Command Line Interface or (2) Graphical User Interface, related to a "code injection" issue.

Weakness: CWE-264

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

It affects 1 product.


Products: Ibm Scale Out Network Attached Storage.

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

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

## Is CVE-2012-2163 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-0706](https://insights.sbomify.com/CVE-2012-0706/): Hardcoded credentials in n/a (low 3.5)
- [CVE-2014-3045](https://insights.sbomify.com/CVE-2014-3045/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2163 is a critical code injection vulnerability in n/a, published on 30 Jul 2012. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-2163 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-2163/ (Markdown: https://insights.sbomify.com/CVE-2012-2163/index.md)
```

## Sources

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

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