# CVE-2011-3180: Command injection in n/a

> Attackers can execute arbitrary commands via shell metacharacters in overlay file paths in SUSE Studio Onsite.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-vq3j-4cjf-gfwg

## What is CVE-2011-3180?

CVE-2011-3180 is a high-severity command injection vulnerability in n/a, published on 16 Apr 2014. It can be exploited over the network, with no action from the victim.

### Official description

kiwi before 4.98.08, as used in SUSE Studio Onsite 1.2 before 1.2.1 and SUSE Studio Extension for System z 1.2 before 1.2.1, allows attackers to execute arbitrary commands via shell metacharacters in the path of an overlay file, related to chown.

## Which versions are affected by CVE-2011-3180?

It affects 3 products.


Products: Suse Kiwi, Suse Studio Extension for System Z, Suse Studio Onsite.

## How do I fix CVE-2011-3180?

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

## Is CVE-2011-3180 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-4192](https://insights.sbomify.com/CVE-2011-4192/): Command injection in n/a (high 7.5)
- [CVE-2011-4195](https://insights.sbomify.com/CVE-2011-4195/): Command injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3180 and fix it if it is affected.

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

## Sources

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

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