# CVE-2020-10627: Missing authorization in Omnipod Insulin Management System

> Attackers can intercept data and modify insulin pump settings due to missing authentication in the RF protocol, posing severe health risks.

- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r26f-v6j2-2h4j

## What is CVE-2020-10627?

CVE-2020-10627 is a high-severity missing authorization vulnerability in Insulet Omnipod Insulin Management System, published on 1 Dec 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Insulet Omnipod Insulin Management System insulin pump product ID 19191 and 40160 is designed to communicate using a wireless RF with an Insulet manufactured Personal Diabetes Manager device. This wireless RF communication protocol does not properly implement authentication or authorization. An attacker with access to one of the affected insulin pump models may be able to modify and/or intercept data. This vulnerability could also allow attackers to change pump settings and control insulin delivery.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2020-10627?

It affects 1 product.


Products: Insulet Omnipod Insulin Management System Firmware.

## How do I fix CVE-2020-10627?

No fix has been published for CVE-2020-10627 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-10627 being exploited?

There is no known exploitation of CVE-2020-10627 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-10627 and fix it if it is affected.

What it is: CVE-2020-10627 is a high-severity missing authorization vulnerability in Insulet Omnipod Insulin Management System, published on 1 Dec 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10627 in the wild and no public exploit code.

Affected product: Insulet Omnipod Insulin Management System. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-10627/ (Markdown: https://insights.sbomify.com/CVE-2020-10627/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-10627
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-10627
- OSV: https://osv.dev/vulnerability/CVE-2020-10627

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-10627/
Summaries are generated and may contain mistakes; the official description above is the record.