Skip to content
Fencer Intel
high 8.8

CVE-2020-27264 json

In SOOIL Developments Co., Ltd Diabecare RS, AnyDana-i and AnyDana-A, the communication protocol of the insulin pump and its AnyDana-i and…

published 5y ago modified 4mo ago also EUVD-2020-19777

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 46%
public exploits
0
none known

Summary

In SOOIL Developments Co., Ltd Diabecare RS, AnyDana-i and AnyDana-A, the communication protocol of the insulin pump and its AnyDana-i and AnyDana-A mobile applications use deterministic keys, which allows unauthenticated, physically proximate attackers to brute-force the keys via Bluetooth Low Energy.

Patch / fix

  • sooil anydana-a_firmware 3.0
  • sooil anydana-i_firmware 3.0
  • sooil diabecare_rs_firmware 3.0

Is CVE-2020-27264 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSMA-21-012-01 updated cvss 7.6

SOOIL Dana Diabecare RS Products

  • SOOIL Developments Co, Ltd. AnyDana-A < 3.0 SOOIL Developments Co, Ltd. AnyDana-i < 3.0 SOOIL Developments Co, Ltd. Dana Diabecare RS < 3.0
    affected: vendor fix

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 3.3 AV:A/AC:L/Au:N/C:P/I:N/A:N

Affected products

  • n/a SOOIL Developments Co., Ltd Diabecare RS, AnyDana-i and AnyDana-A

Classification

Weakness
  • CWE-330 Use of Insufficiently Random Values

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.