CVE-2020-27272
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedSOOIL Developments CoLtd DiabecareRS, AnyDana-i, AnyDana-A, The communication protocol of the insulin pump and AnyDana-i,AnyDana-A mobile apps doesn't use adequate measures to authenticate the pump before exchanging keys, which allows unauthenticated, physically proximate attackers to eavesdrop the keys and spoof the pump via BLE.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe insulin pump and its companion mobile apps use a BLE (Bluetooth Low Energy) communication protocol that lacks proper pump authentication before initiating key exchange. An attacker within BLE range can passively eavesdrop the key exchange process to capture authentication keys, then use those keys to spoof the legitimate pump and send unauthorized commands (e.g., insulin delivery instructions) to the mobile app.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.0< 3.0< 3.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the insulin pump modelInspect the pump device, its packaging, or the companion mobile app to confirm the specific model (Sooil Anydana A, Anydana I, or Diabecare Rs)Affected if The device is one of these three affected models and the firmware version is below 3.0
-
Determine the installed firmware versionAccess the pump's on-device menu (typically under Settings > Device Info or System Info) to view the current firmware version numberAffected if Firmware version displayed is less than 3.0 (for example, 2.x.x series)
-
Verify BLE communication is activeCheck the pump's BLE settings menu or inspect the companion mobile app's connection status to confirm Bluetooth Low Energy pairing is enabled and actively connectedAffected if BLE is enabled and the pump is communicating with the mobile app, making it susceptible to passive eavesdropping during key exchange
The environment is affected if the insulin pump is a Sooil Anydana A, Anydana I, or Diabecare Rs model running firmware version below 3.0 with BLE communication actively enabled.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data3.0
Implement mutual authentication requiring the pump to prove its identity before key exchange begins, such as using pre-shared secrets or certificate-based authentication. Deploy firmware updates to affected pumps and app updates through the vendor's update mechanism.
- Consultation16.0 h
- Implementation40.0 h
- Testing32.0 h
- Review / QA24.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $31,232.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-27272 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-27272 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data