# CVE-2017-8330: Denial of service in n/a

> A remote attacker can crash the miniupnpd process on Securifi Almond routers by sending a large payload to the NewInMessage SOAP parameter.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jfgg-vc2q-w48v

## What is CVE-2017-8330?

CVE-2017-8330 is a medium-severity denial of service vulnerability in n/a, published on 18 Jun 2019. It can only be exploited from the same machine or local 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 UPnP functionality for devices to interface with the router and interact with the device. It seems that the "NewInMessage" SOAP parameter passed with a huge payload results in crashing the process. 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 "miniupnpd" is the one that has the vulnerable function that receives the values sent by the SOAP request. If we open this binary in IDA-pro we will notice that this follows a MIPS little endian format. The function WscDevPutMessage at address 0x0041DBB8 in IDA pro is identified to be receiving the values sent in the SOAP request. The SOAP parameter "NewInMesage" received at address 0x0041DC30 causes the miniupnpd process to finally crash when a second request is sent to the same process.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 3 products.


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

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

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

## Is CVE-2017-8330 being exploited?

There is no known exploitation of CVE-2017-8330 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-8333](https://insights.sbomify.com/CVE-2017-8333/): Command injection in n/a (high 8.8)
- [CVE-2017-8336](https://insights.sbomify.com/CVE-2017-8336/): Memory corruption in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-8330 is a medium-severity denial of service vulnerability in n/a, published on 18 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-8330 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-8330/ (Markdown: https://insights.sbomify.com/CVE-2017-8330/index.md)
```

## Sources

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

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