CVE-2019-10964: Medtronic MiniMed 508 and Paradigm Series Insulin Pumps Improper Access Control
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.2% (FIRST EPSS); higher than 68.8% of all records.
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Medtronic MiniMed Insulin Pumps are designed to communicate using a wireless RF with other devices, such as blood glucose meters, glucose sensor transmitters, and CareLink USB devices. This wireless RF communication protocol does not properly implement authentication or authorization. An attacker with adjacent access to one of the affected insulin pump models can inject, replay, modify, and/or intercept data. This vulnerability could also allow attackers to change pump settings and control insulin delivery.
- Published
- Jun 28, 2019
- Updated
- Jun 16, 2026
- EPSS
- 1.2% · 68th percentile
- CWE
- CWE-284
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.2%
CNA vs NVD score
- NVD
- —
- CNA · icscert
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| medtronic | minimed 508 firmware | cpe:2.3:o:medtronic:minimed_508_firmware |
| medtronic | minimed 508 | cpe:2.3:h:medtronic:minimed_508 |
| medtronic | minimed paradigm 511 firmware | cpe:2.3:o:medtronic:minimed_paradigm_511_firmware |
| medtronic | minimed paradigm 511 | cpe:2.3:h:medtronic:minimed_paradigm_511 |
| medtronic | minimed paradigm 512 firmware | cpe:2.3:o:medtronic:minimed_paradigm_512_firmware |
| medtronic | minimed paradigm 512 | cpe:2.3:h:medtronic:minimed_paradigm_512 |
| medtronic | minimed paradigm 712 firmware | cpe:2.3:o:medtronic:minimed_paradigm_712_firmware |
| medtronic | minimed paradigm 712 | cpe:2.3:h:medtronic:minimed_paradigm_712 |
| medtronic | minimed paradigm 712e firmware | cpe:2.3:o:medtronic:minimed_paradigm_712e_firmware |
| medtronic | minimed paradigm 712e | cpe:2.3:h:medtronic:minimed_paradigm_712e |
| medtronic | minimed paradigm 515 firmware | cpe:2.3:o:medtronic:minimed_paradigm_515_firmware |
| medtronic | minimed paradigm 515 | cpe:2.3:h:medtronic:minimed_paradigm_515 |
and 26 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- medtronic minimed 508 firmwareall versions
- medtronic minimed paradigm 511 firmwareall versions
- medtronic minimed paradigm 512 firmwareall versions
- medtronic minimed paradigm 515 firmwareall versions
- medtronic minimed paradigm 522 firmwareall versions
- medtronic minimed paradigm 522k firmwareall versions
- medtronic minimed paradigm 523 firmwareup to 2.4a inclusive
- medtronic minimed paradigm 523k firmwareup to 2.4a inclusive
- medtronic minimed paradigm 712 firmwareall versions
- medtronic minimed paradigm 712e firmwareall versions
- medtronic minimed paradigm 715 firmwareall versions
- medtronic minimed paradigm 722 firmwareall versions
- medtronic minimed paradigm 722k firmwareall versions
- medtronic minimed paradigm 723 firmwareup to 2.4a inclusive
- medtronic minimed paradigm 723k firmwareup to 2.4a inclusive
- medtronic minimed paradigm veo 554 firmwareup to 2.6a inclusive
- medtronic minimed paradigm veo 554cm firmwareup to 2.7a inclusive
- medtronic minimed paradigm veo 754 firmwareup to 2.6a inclusive
- medtronic minimed paradigm veo 754cm firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (icscert). Independent of NVD's CPE analysis and usually ahead of it.
Medtronic MiniMed 508 pump
- All versionsaffected
Medtronic MiniMed Paradigm 511 pump
- All versionsaffected
Medtronic MiniMed Paradigm 512/712 pumps
- All versionsaffected
Medtronic MiniMed Paradigm 515/715 pumps
- All versionsaffected
Medtronic MiniMed Paradigm 522/722 pumps
- All versionsaffected
Medtronic MiniMed Paradigm 522K/722K pumps
- All versionsaffected
Medtronic MiniMed Paradigm 523/723 pumps
- up to and including Software Versions 2.4Aaffected
Medtronic MiniMed Paradigm 523K/723K pumps
- up to and including Software Versions 2.4Aaffected
Medtronic MiniMed Paradigm 712E pump
- All versionsaffected
Medtronic MiniMed Paradigm Veo 554/754 pumps
- up to and including Software Versions 2.6Aaffected
Medtronic MiniMed Paradigm Veo 554CM/754CM pumps
- up to and including Software Versions 2.7Aaffected
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Based on earlier work performed by external researchers including Nathanael Paul, Jay Radcliffe, and Barnaby Jack, andrecent work performed by external researchers Billy Rios, Jonathan Butts, anfinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- low · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- High
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-284 · Improper Access ControlCVSS vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Embedding Scripts within ScriptsCAPEC-19likelihood: High · High
- Malicious Logic InsertionCAPEC-441likelihood: Medium · High
- Modification of Windows Service ConfigurationCAPEC-478likelihood: Low · High
- Malicious Root CertificateCAPEC-479likelihood: Low · Low
- Intent SpoofCAPEC-502
- WebView ExposureCAPEC-503
- Data Injected During ConfigurationCAPEC-536likelihood: Low · High
- Incomplete Data Deletion in a Multi-Tenant EnvironmentCAPEC-546likelihood: Low · Medium
ATT&CK techniques
- RootkitT1014
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Initialization ScriptsT1037
- Taint shared contentT1080
- Server Software Component: Terminal Services DLLT1505.005
- Pre-OS Boot:BootkitT1542.003
- Create or Modify System ProcessT1543
- Create or Modify System Process: Launch AgentT1543.001
- Create or Modify System Process:Windows ServiceT1543.003
- Create or Modify System Process: Launch DaemonT1543.004
- Event Triggered Execution:Change Default File AssociationT1546.001
- Event Triggered Execution:.bash_profile and .bashrcT1546.004
- Event Triggered Execution: Accessibility FeaturesT1546.008
- Event Triggered Execution: Installer PackagesT1546.016
- Boot or Logon Autostart ExecutionT1547
- Boot or Logon Autostart Execution:Kernel Modules and ExtensionsT1547.006
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.