# CVE-2017-8333: Command injection in n/a

> Attackers can execute arbitrary commands on Securifi Almond routers via the route addition feature, potentially taking full control of the device.

- **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:** 18 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xmqw-gc65-wj6q

## What is CVE-2017-8333?

CVE-2017-8333 is a high-severity command injection vulnerability in n/a, published on 18 Jun 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered on Securifi Almond, Almond+, and Almond 2015 devices with firmware AL-R096. The device provides a user with the capability of adding new routes to the device. It seems that the POST parameters passed in this request to set up routes on the device can be set in such a way that would result in passing commands to a "popen" API in the function and thus result in command injection on the device. If the firmware version AL-R096 is dissected using binwalk tool, we obtain a cpio-root archive which contains the filesystem set up on the device that contains all the binaries. The binary "goahead" is the one that has the vulnerable function that receives the values sent by the POST request. If we open this binary in IDA-pro we will notice that this follows a MIPS little endian format. The function sub_00420F38 in IDA pro is identified to be receiving the values sent in the POST request and the value set in POST parameter "dest" is extracted at address 0x00420FC4. The POST parameter "dest is concatenated in a route add command and this is passed to a "popen" function at address 0x00421220. This allows an attacker to provide the payload of his/her choice and finally take control of the device.

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

## Which versions are affected by CVE-2017-8333?

It affects 3 products.


Products: Securifi Almond\+firmware, Securifi Almond 2015 Firmware, Securifi Almond Firmware.

## How do I fix CVE-2017-8333?

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

## Is CVE-2017-8333 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-8328](https://insights.sbomify.com/CVE-2017-8328/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2017-8331](https://insights.sbomify.com/CVE-2017-8331/): Command injection in n/a (high 8.8)
- [CVE-2017-8332](https://insights.sbomify.com/CVE-2017-8332/): Cross-site scripting in n/a (high 8.8)
- [CVE-2017-8336](https://insights.sbomify.com/CVE-2017-8336/): Memory corruption in n/a (high 8.8)
- [CVE-2017-8337](https://insights.sbomify.com/CVE-2017-8337/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8333 and fix it if it is affected.

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

## Sources

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

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