# CVE-2015-2279: Command injection in n/a

> Remote attackers can execute arbitrary OS commands on AirLive devices via shell metacharacters in specific CGI parameters.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jul 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5f23-7wg5-v6qm

## What is CVE-2015-2279?

CVE-2015-2279 is a critical command injection vulnerability in n/a, published on 24 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

cgi_test.cgi in AirLive BU-2015 with firmware 1.03.18, BU-3026 with firmware 1.43, and MD-3025 with firmware 1.81 allows remote attackers to execute arbitrary OS commands via shell metacharacters after an "&" (ampersand) in the write_mac write_pid, write_msn, write_tan, or write_hdv parameter.

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

## Which versions are affected by CVE-2015-2279?

It affects 3 products.


Products: Airlive Bu-2015 Firmware, Airlive Bu-3026 Firmware, Airlive Md-3025 Firmware.

## How do I fix CVE-2015-2279?

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

## Is CVE-2015-2279 being exploited?

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

Public exploit code:

- AirLive (Multiple Products) - OS Command Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-8389](https://insights.sbomify.com/CVE-2014-8389/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2279 and fix it if it is affected.

What it is: CVE-2015-2279 is a critical command injection vulnerability in n/a, published on 24 Jul 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2015-2279 exists.

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-2015-2279/ (Markdown: https://insights.sbomify.com/CVE-2015-2279/index.md)
```

## Sources

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

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