CVE-2017-9391 Memory corruption in n/a

High 8.8 Published 17 Jun 2019 Updated 5 Aug 2024

An attacker can execute arbitrary code on Vera home automation devices by sending a long URL parameter to the UPnP image request service, causing a stack buffer overflow.

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-9391?

CVE-2017-9391 is a high-severity memory corruption vulnerability in n/a, published on 17 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 Vera VeraEdge 1.7.19 and Veralite 1.7.481 devices. The device provides UPnP services that are available on port 3480 and can also be accessed via port 80 using the url "/port_3480". It seems that the UPnP services provide "request_image" as one of the service actions for a normal user to retrieve an image from a camera that is controlled by the controller. It seems that the "URL" parameter passed in the query string is not sanitized and is stored on the stack which allows an attacker to overflow the buffer. The function "LU::Generic_IP_Camera_Manager::REQ_Image" is activated when the lu_request_image is passed as the "id" parameter in query string. This function then calls "LU::Generic_IP_Camera_Manager::GetUrlFromArguments" and passes a "pointer" to the function where it will be allowed to store the value from the URL parameter. This pointer is passed as the second parameter $a2 to the function "LU::Generic_IP_Camera_Manager::GetUrlFromArguments". However, neither the callee or the caller in this case performs a simple length check and as a result an attacker who is able to send more than 1336 characters can easily overflow the values stored on the stack including the $RA value and thus execute code on the device.

Weakness: CWE-119

Which versions are affected by CVE-2017-9391?

It affects 2 products.

Products include Getvera Veraedge Firmware, Getvera Veralite Firmware.

How do I fix CVE-2017-9391?

No fix has been published for CVE-2017-9391 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-9391 being exploited?

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

Sources

Also known as GHSA-8rhq-jr33-p7r3.