# CVE-2017-8335: Memory corruption in n/a > A stack-based buffer overflow in the Securifi Almond router firmware allows remote attackers to execute arbitrary code via a large POST parameter. - **Severity:** High 8.0 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/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:** A user has to click or open something - **Fix available:** No - **Published:** 18 Jun 2019 - **Updated:** 5 Aug 2024 - **Also known as:** GHSA-8gcv-7mx7-pfhc ## What is CVE-2017-8335? CVE-2017-8335 is a high-severity memory corruption vulnerability in n/a, published on 18 Jun 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### 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 setting name for wireless network. These values are stored by the device in NVRAM (Non-volatile RAM). It seems that the POST parameters passed in this request to set up names on the device do not have a string length check on them. This allows an attacker to send a large payload in the "mssid_1" POST parameter. The device also allows a user to view the name of the Wifi Network set by the user. While processing this request, the device calls a function named "getCfgToHTML" at address 0x004268A8 which retrieves the value set earlier by "mssid_1" parameter as SSID2 and this value then results in overflowing the stack set up for this function and allows an attacker to control $ra register value on the stack which allows an attacker to control the device by executing a payload of an attacker's choice. 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 recieves 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 parameter "mssid_1" at address 0x0042BA00 and then sets in the NVRAM at address 0x0042C314. The value is later retrieved in the function "getCfgToHTML" at address 0x00426924 and this results in overflowing the buffer due to "strcat" function that is utilized by this function. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2017-8335? It affects 3 products. Products: Securifi Almond\+firmware, Securifi Almond 2015 Firmware, Securifi Almond Firmware. ## How do I fix CVE-2017-8335? No fix has been published for CVE-2017-8335 yet. Limit exposure of the affected software until one is available. ## Is CVE-2017-8335 being exploited? There is no known exploitation of CVE-2017-8335 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-8335 and fix it if it is affected. What it is: CVE-2017-8335 is a high-severity memory corruption vulnerability in n/a, published on 18 Jun 2019. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2017-8335 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-8335/ (Markdown: https://insights.sbomify.com/CVE-2017-8335/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-8335 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-8335 - OSV: https://osv.dev/vulnerability/CVE-2017-8335 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-8335/ Summaries are generated and may contain mistakes; the official description above is the record.