# CVE-2017-11580: Memory corruption in n/a

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

- **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:** 2 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-857g-5g59-pwmx

## 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: 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.

## Is CVE-2017-11580 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-11579](https://insights.sbomify.com/CVE-2017-11579/): In the most recent firmware for Blipcare, the device provides an open Wireless network called "Blip" for communicating with the device. (high 7.1)
- [CVE-2017-11578](https://insights.sbomify.com/CVE-2017-11578/): Information disclosure in n/a (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: 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.
Exploitation: There is no known exploitation of CVE-2017-11580 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-11580/ (Markdown: https://insights.sbomify.com/CVE-2017-11580/index.md)
```

## Sources

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

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