CVE-2017-8336 Memory corruption in n/a
Stack-based buffer overflow in Securifi Almond routers allows remote attackers to execute arbitrary code via crafted POST parameters.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2017-8336?
CVE-2017-8336 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, 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 overflowing the stack set up and allow an attacker to control the $ra register stored on the stack. 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 request. The POST parameter "gateway" allows to overflow the stack and control the $ra register after 1546 characters. The value from this post parameter is then copied on the stack at address 0x00421348 as shown below. This allows an attacker to provide the payload of his/her choice and finally take control of the device.
Weakness: CWE-119
Which versions are affected by CVE-2017-8336?
It affects 3 products.
Products include Securifi Almond\+firmware, Securifi Almond 2015 Firmware, Securifi Almond Firmware.
How do I fix CVE-2017-8336?
No fix has been published for CVE-2017-8336 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2017-8336 being exploited?
There is no known exploitation of CVE-2017-8336 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-pv4f-9pgh-pj73.