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

> Remote attackers can execute arbitrary code on systems running the Novell iPrint Client by exploiting the op-client-interface-version action.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Dec 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-7cm2-g3r8-rf95

## What is CVE-2012-0411?

CVE-2012-0411 is a critical code injection vulnerability in n/a, published on 24 Dec 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Unspecified vulnerability in Novell iPrint Client before 5.82 allows remote attackers to execute arbitrary code via an op-client-interface-version action.

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

It affects 1 product.


Products: Novell Iprint.

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

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

## Is CVE-2012-0411 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-1091](https://insights.sbomify.com/CVE-2013-1091/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-4185](https://insights.sbomify.com/CVE-2011-4185/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-4187](https://insights.sbomify.com/CVE-2011-4187/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-0935](https://insights.sbomify.com/CVE-2008-0935/): Memory corruption in n/a (critical 10.0)
- [CVE-2011-4186](https://insights.sbomify.com/CVE-2011-4186/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-0411 is a critical code injection vulnerability in n/a, published on 24 Dec 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-0411 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-0411/ (Markdown: https://insights.sbomify.com/CVE-2012-0411/index.md)
```

## Sources

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

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