# CVE-2016-2278: Command injection in n/a

> Authenticated administrators can execute arbitrary OS commands by bypassing the Minimal Shell protection mechanism in Schneider Electric Struxureware Building Operations.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Mar 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5242-5wvm-8m3p

## What is CVE-2016-2278?

CVE-2016-2278 is a high-severity command injection vulnerability in n/a, published on 2 Mar 2016. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Schneider Electric Struxureware Building Operations Automation Server AS 1.7 and earlier and AS-P 1.7 and earlier allows remote authenticated administrators to execute arbitrary OS commands by defeating an msh (aka Minimal Shell) protection mechanism.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2016-2278?

It affects 2 products.


Products: Schneider-Electric Struxureware Building Operations Automation Server As-P Firmware, Schneider-Electric Struxureware Building Operations Automation Server as Firmware.

## How do I fix CVE-2016-2278?

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

## Is CVE-2016-2278 being exploited?

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

Public exploit code:

- Schneider Electric SBO / AS - Multiple Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-2278 and fix it if it is affected.

What it is: CVE-2016-2278 is a high-severity command injection vulnerability in n/a, published on 2 Mar 2016. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-2278 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-2016-2278/ (Markdown: https://insights.sbomify.com/CVE-2016-2278/index.md)
```

## Sources

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

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