CVE-2017-11580 Memory corruption in n/a

Medium 6.5 Published Updated

A memory corruption vulnerability in Blipcare Wifi blood pressure monitors allows remote attackers to cause a denial of service via large HTTP headers.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Local or same network only
Victim action needed
Not needed
Fix
None listed

What is CVE-2017-11580?

CVE-2017-11580 is a medium-severity memory corruption vulnerability in n/a, published on 2 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

Blipcare Wifi blood pressure monitor BP700 10.1 devices allow memory corruption that results in Denial of Service. When connected to the "Blip" open wireless connection provided by the device, if a large string is sent as a part of the HTTP request in any part of the HTTP headers, the device could become completely unresponsive. Presumably this happens as the memory footprint provided to this device is very small. According to the specs from Rezolt, the Wi-Fi module only has 256k of memory. As a result, an incorrect string copy operation using either memcpy, strcpy, or any of their other variants could result in filling up the memory space allocated to the function executing and this would result in memory corruption. To test the theory, one can modify the demo application provided by the Cypress WICED SDK and introduce an incorrect "memcpy" operation and use the compiled application on the evaluation board provided by Cypress semiconductors with exactly the same Wi-Fi SOC. The results were identical where the device would completely stop responding to any of the ping or web requests.

Weakness: CWE-399

Which versions are affected by CVE-2017-11580?

It affects 1 product.

Products include Blipcare Wi-Fi Blood Pressure Monitor Firmware.

How do I fix CVE-2017-11580?

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

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

Sources

Also known as GHSA-857g-5g59-pwmx.

Is CVE-2017-11580 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free