Blipcare Wifi blood pressure monitor BP700 10.1 devices allow memory corruption that results in Denial of Service
Published Jul 2, 2019
6.5
MEDIUMCVSS 3.0
EPSS 1.43%
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.
Affected products
No data.
- ≤ bp700_10.1
Running on/with
- n/a
No data.
No Red Hat product state for this CVE.
No package ranges for this CVE.
Remediation
No remediation recorded yet.
Metrics
No CVSS v4.0 score for this CVE.
No CVSS v3.1 score for this CVE.
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
AV:A/AC:L/Au:N/C:N/I:N/A:C
This CVE is not in the KEV list.
No CISA SSVC assessment for this CVE yet.
Estimated probability of exploitation in the wild in the next 30 days (FIRST EPSS). As of Oct 1, 2026.
Score over time
2021–2026- EPSS v1
- EPSS v5
- EPSS v2
- EPSS v3
Percentile over time
- EPSS v1
- EPSS v5
- EPSS v2
- EPSS v3
Table of values (11 key points)
Flat stretches are collapsed; showing up to 120 newest points.
| Date | Score | Percentile | Model |
|---|---|---|---|
| Oct 1, 2026 | 1.43% (0.01431) | 72.08th | v5 (v2026.06.15) |
| Sep 20, 2026 | 1.43% (0.01431) | 71.86th | v5 (v2026.06.15) |
| Jul 20, 2024 | 0.26% (0.00260) | 66.17th | v3 (v2023.03.01) |
| Jul 13, 2024 | 0.26% (0.00260) | 66.13th | v3 (v2023.03.01) |
| Jun 25, 2024 | 0.37% (0.00370) | 72.73th | v3 (v2023.03.01) |
| Feb 8, 2024 | 0.31% (0.00312) | 69.31th | v3 (v2023.03.01) |
| Mar 7, 2023 | 0.31% (0.00312) | 65.38th | v3 (v2023.03.01) |
| Mar 6, 2023 | 0.95% (0.00954) | 36.37th | v2 (v2022.01.01) |
| Feb 4, 2022 | 0.95% (0.00954) | 16.28th | v2 (v2022.01.01) |
| Feb 3, 2022 | 0.90% (0.00900) | 25.44th | v5 (v2026.06.15) |
| Apr 14, 2021 | 0.90% (0.00900) | 0.00th | v1 |
References (3)
- http://packetstormsecurity.com/files/153225/Blipcare-Clear-Text-Communication-Memory-Corruption.html x_refsource_MISCThird Party AdvisoryVDB Entry
- https://github.com/ethanhunnt/IoT_vulnerabilities/blob/master/Blipcare_sec_issues.pdf x_refsource_MISCExploitThird Party Advisory
- https://seclists.org/bugtraq/2019/Jun/8 mailing-listx_refsource_BUGTRAQMailing ListThird Party Advisory
| Link | Providers | Tags |
|---|---|---|
| http://packetstormsecurity.com/files/153225/Blipcare-Clear-Text-Communication-Memory-Corruption.html | x_refsource_MISCThird Party AdvisoryVDB Entry | |
| https://github.com/ethanhunnt/IoT_vulnerabilities/blob/master/Blipcare_sec_issues.pdf | x_refsource_MISCExploitThird Party Advisory | |
| https://seclists.org/bugtraq/2019/Jun/8 | mailing-listx_refsource_BUGTRAQMailing ListThird Party Advisory |
Change history (0)
No recorded changes yet.