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

> Authenticated attackers can execute arbitrary OS commands on AirLink101 SkyIPCam1620W cameras via shell metacharacters in the mac parameter.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A: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:** 24 Jul 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-9xpp-pm7c-3qwm

## What is CVE-2015-2280?

CVE-2015-2280 is a high-severity command injection vulnerability in n/a, published on 24 Jul 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

snwrite.cgi in AirLink101 SkyIPCam1620W Wireless N MPEG4 3GPP network camera with firmware FW_AIC1620W_1.1.0-12_20120709_r1192.pck allows remote authenticated users to execute arbitrary OS commands via shell metacharacters in the mac parameter.

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

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

It affects 1 product.


Products: Airlink101 Skyipcam1620w Wireless N Mpeg4 3gpp Firmware.

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

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

## Is CVE-2015-2280 being exploited?

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

Public exploit code:

- AirLink101 SkyIPCam1620W - OS Command Injection (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-2280 is a high-severity command injection vulnerability in n/a, published on 24 Jul 2017. 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-2015-2280 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-2280/ (Markdown: https://insights.sbomify.com/CVE-2015-2280/index.md)
```

## Sources

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

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