LiveActive security incident?Get immediate response
CVE Record

CVE-2017-11578: It was discovered as a part of the research on IoT devices in the most recent firmware for Blipcare device...

It was discovered as a part of the research on IoT devices in the most recent firmware for Blipcare device that the device allows to connect to web management interface on a non-SSL connection using plain text HTTP protocol. The user uses the web management interface of the device to provide the user's Wi-Fi credentials so that the device can connect to it and have Internet access. This device acts as a Wireless Blood pressure monitor and is used to measure blood pressure levels of a person. This allows an attacker who is connected to the Blipcare's device wireless network to easily sniff these values using a MITM attack.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This CVE describes a Blipcare wireless blood pressure monitor setup interface using plain HTTP instead of SSL/TLS. During Wi-Fi setup, credentials may be exposed to someone already connected to the device’s wireless network. The business risk is credential disclosure, not confirmed remote compromise. Exposure appears limited to Blipcare wireless blood pressure monitors using the affected web management setup flow. Evidence does not identify exact model numbers, firmware versions, deployment counts, or other Blipcare products. Treat this as a targeted IoT exposure issue. Prioritize if Blipcare devices are used in clinical, workplace health, or managed residential environments where Wi-Fi credential disclosure could enable broader network access. Mitigation focus: Check Blipcare or distributor guidance for firmware updates or setup changes.; Provision the device only on trusted networks and controlled physical premises.; Rotate Wi-Fi credentials if setup occurred in an untrusted environment..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2017-11578 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.