# CVE-2012-10040: Openfiler v2.x NetworkCard Command Execution

> Authenticated attackers can execute arbitrary commands via unsanitized input in Openfiler, escalating privileges to root due to misconfigured sudoers.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **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:** 11 Aug 2025
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-vxcv-gc68-4r3q

## What is CVE-2012-10040?

CVE-2012-10040 is a critical command injection vulnerability in Openfiler, published on 11 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Openfiler v2.x contains a command injection vulnerability in the system.html page. The device parameter is used to instantiate a NetworkCard object, whose constructor in network.inc calls exec() with unsanitized input. An authenticated attacker can exploit this to execute arbitrary commands as the openfiler user. Due to misconfigured sudoers, the openfiler user can escalate privileges to root via sudo /bin/bash without a password.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2012-10040 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-10040 exists.

Public exploit code:

- Openfiler v2.x NetworkCard Command Execution (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-10040 is a critical command injection vulnerability in Openfiler, published on 11 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-10040 exists.

Affected product: Openfiler. 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-10040/ (Markdown: https://insights.sbomify.com/CVE-2012-10040/index.md)
```

## Sources

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

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