LiveActive security incident?Get immediate response
CVE Record

CVE-2020-27373: Dr Trust USA iCheck Connect BP Monitor BP Testing 118 1.2.1 is vulnerable to Plain text command over BLE.

Dr Trust USA iCheck Connect BP Monitor BP Testing 118 1.2.1 is vulnerable to Plain text command over BLE.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-27373 reports that the Dr Trust USA iCheck Connect BP Monitor BP Testing 118 version 1.2.1 uses plaintext commands over Bluetooth Low Energy. In practical terms, nearby Bluetooth-range parties may be able to observe or interact with device communications. Public data does not provide CVSS scoring, confirmed impact details, or a vendor fix.

Executive priority

Treat this as a targeted device-risk issue, not a broad enterprise emergency. Prioritize if these monitors are used in clinical, occupational health, or regulated workflows where measurement trust matters. The main gap is lack of public remediation and impact detail.

Technical view

The CVE description identifies plaintext command transmission over BLE in Dr Trust USA iCheck Connect BP Monitor BP Testing 118 1.2.1. The record has no listed CWE, CVSS, CPE, or detailed affected-version metadata. The cited Medium write-up appears to be the primary technical reference; vendor product page confirms the product context, not remediation.

Likely exposure

Exposure is most likely limited to environments where the affected blood pressure monitor and its BLE-connected app/device are in use. Attack opportunity appears proximity-based because BLE generally requires radio range. Internet-wide exposure is not indicated by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing, public active exploitation, exploit availability, or confirmed real-world abuse. The practical risk depends on BLE proximity, pairing behavior, command sensitivity, and whether plaintext commands can alter readings, device state, or data handling.

Researcher notes

The public CVE metadata is sparse: no CVSS, CWE, CPE, or vendor advisory is included. Avoid assuming command effects beyond plaintext BLE exposure. Further validation should focus on affected-version confirmation, BLE security properties, and whether vendor-supported updates or replacements exist.

Mitigation direction

  • Check Dr Trust guidance or support channels for firmware, app, or product updates.
  • Inventory use of Dr Trust iCheck Connect BP Monitor BP Testing 118 1.2.1.
  • Limit use in untrusted public or crowded Bluetooth environments where feasible.
  • Disable Bluetooth when the monitor is not actively being used, if supported.
  • Segregate clinical workflows from unvalidated consumer BLE medical devices where possible.

Validation and detection

  • Confirm whether the organization uses the named Dr Trust monitor and version 1.2.1.
  • Review device/app documentation for BLE security, pairing, and update mechanisms.
  • Check vendor support pages for advisories, firmware notes, or replacement guidance.
  • Assess whether local policy allows plaintext BLE medical device communications.
  • Document compensating controls for any continued use.
Prepared
Confidence
medium
Sources
4

Public sources used

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-2020-27373 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
3Timeline events
1ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

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.