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

> Authenticated attackers can execute arbitrary CLI commands on Genexis devices via the Parental Control panel parameters.

- **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:** 5 Jan 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-56xv-9v42-q2cf

## What is CVE-2015-3441?

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

### Official description

The Parental Control panel in Genexis devices with DRGOS before 1.14.1 allows remote authenticated users to execute arbitrary CLI commands via the (1) start_hour, (2) start_minute, (3) end_hour, (4) end_minute, or (5) hostname parameter.

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

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

It affects 1 product.


Products: Genexia Drgos.

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

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

## Is CVE-2015-3441 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-3441 is a high-severity command injection vulnerability in n/a, published on 5 Jan 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-3441 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-3441/ (Markdown: https://insights.sbomify.com/CVE-2015-3441/index.md)
```

## Sources

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

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