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

> Authenticated attackers can execute arbitrary commands on NetCommWireless HSPA 3G10WVE routers via shell metacharacters in the DIA_IPADDRESS parameter.

- **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:** 9 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r5j6-vjxh-3v3w

## What is CVE-2015-6024?

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

### Official description

ping.cgi in NetCommWireless HSPA 3G10WVE wireless routers with firmware before 3G10WVE-L101-S306ETS-C01_R05 allows remote authenticated users to execute arbitrary commands via shell metacharacters in the DIA_IPADDRESS parameter.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 1 product.


Products: Netcommwireless Hspa 3g10wve Firmware.

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

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

## Is CVE-2015-6024 being exploited?

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

Public exploit code:

- NetCommWireless HSPA 3G10WVE Wireless Router - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2015-6023](https://insights.sbomify.com/CVE-2015-6023/): Auth bypass in n/a (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-6024 is a critical command injection vulnerability in n/a, published on 9 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-6024 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-2015-6024/ (Markdown: https://insights.sbomify.com/CVE-2015-6024/index.md)
```

## Sources

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

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