CVE-2022-32537: Medtronic MiniMed 600 Series Pump System Communication Issue
Noroxi assessment
Priority: Monitor (action score 19/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: 0.34% (FIRST EPSS).
- Someone on the same network segment can trigger it. A low-privileged account is enough. 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
A vulnerability exists which could allow an unauthorized user to learn aspects of the communication protocol used to pair system components while the pump is being paired with other system components. Exploitation requires nearby wireless signal proximity with the patient and the device; advanced technical knowledge is required for exploitation. Please refer to the Medtronic Product Security Bulletin for guidance
- Published
- Dec 12, 2022
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 28th percentile
- CWE
- CWE-693
Report tools
Action score
19
Monitor
Low priority for now.
- CVSS
- 19 / 40 · 4.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 4.8
- CNA · Medtronic
- 4.8
- agree
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 | guardian link 2 transmitter mmt-7730 firmware | cpe:2.3:o:medtronic:guardian_link_2_transmitter_mmt-7730_firmware |
| medtronic | guardian link 2 transmitter mmt-7730 | cpe:2.3:h:medtronic:guardian_link_2_transmitter_mmt-7730 |
| medtronic | guardian link 2 transmitter mmt-7731 firmware | cpe:2.3:o:medtronic:guardian_link_2_transmitter_mmt-7731_firmware |
| medtronic | guardian link 2 transmitter mmt-7731 | cpe:2.3:h:medtronic:guardian_link_2_transmitter_mmt-7731 |
| medtronic | guardian link 2 transmitter mmt-7738 firmware | cpe:2.3:o:medtronic:guardian_link_2_transmitter_mmt-7738_firmware |
| medtronic | guardian link 2 transmitter mmt-7738 | cpe:2.3:h:medtronic:guardian_link_2_transmitter_mmt-7738 |
| medtronic | guardian link 2 transmitter mmt-7775 firmware | cpe:2.3:o:medtronic:guardian_link_2_transmitter_mmt-7775_firmware |
| medtronic | guardian link 2 transmitter mmt-7775 | cpe:2.3:h:medtronic:guardian_link_2_transmitter_mmt-7775 |
| medtronic | guardian link 3 transmitter mmt-7810 firmware | cpe:2.3:o:medtronic:guardian_link_3_transmitter_mmt-7810_firmware |
| medtronic | guardian link 3 transmitter mmt-7810 | cpe:2.3:h:medtronic:guardian_link_3_transmitter_mmt-7810 |
| medtronic | guardian link 3 transmitter mmt-7811 firmware | cpe:2.3:o:medtronic:guardian_link_3_transmitter_mmt-7811_firmware |
| medtronic | guardian link 3 transmitter mmt-7811 | cpe:2.3:h:medtronic:guardian_link_3_transmitter_mmt-7811 |
and 44 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- medtronic guardian link 2 transmitter mmt-7730 firmwareall versions
- medtronic guardian link 2 transmitter mmt-7731 firmwareall versions
- medtronic guardian link 2 transmitter mmt-7738 firmwareall versions
- medtronic guardian link 2 transmitter mmt-7775 firmwareall versions
- medtronic guardian link 3 transmitter mmt-7810 firmwareall versions
- medtronic guardian link 3 transmitter mmt-7811 firmwareall versions
- medtronic minimed 620g mmt-1750 firmwareall versions
- medtronic minimed 630g mmt-1715 firmwareall versions
- medtronic minimed 630g mmt-1754 firmwareall versions
- medtronic minimed 630g mmt-1755 firmwareall versions
- medtronic minimed 640g mmt-1711 firmwareall versions
- medtronic minimed 640g mmt-1712 firmwareall versions
- medtronic minimed 640g mmt-1751 firmwareall versions
- medtronic minimed 640g mmt-1752 firmwareall versions
- medtronic minimed 670g mmt-1740 firmwareall versions
- medtronic minimed 670g mmt-1741 firmwareall versions
- medtronic minimed 670g mmt-1742 firmwareall versions
- medtronic minimed 670g mmt-1760 firmwareall versions
- medtronic minimed 670g mmt-1761 firmwareall versions
- medtronic minimed 670g mmt-1762 firmwareall versions
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Medtronic). Independent of NVD's CPE analysis and usually ahead of it.
Medtronic Minimed 600 Series Insulin Pump
- 620G, 630G, 640G, 670Gaffected
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.
No history yet (it accumulates with the daily EPSS job).
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.
No credits in the CNA record.
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.
- A low-privileged account is enough.
- No user action is required.
- Special conditions such as timing or configuration are required.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Adjacent
- Attack complexity
- High
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-693 · Protection Mechanism FailureCVSS vector
CVSS:3.1/AV:A/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
nvd-primary
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)
- Accessing Functionality Not Properly Constrained by ACLsCAPEC-1likelihood: High · High
- Cross Site TracingCAPEC-107likelihood: Medium · Very High
- Directory IndexingCAPEC-127likelihood: High · Medium
- Using Malicious FilesCAPEC-17likelihood: High · Very High
- Encryption Brute ForcingCAPEC-20likelihood: Low · Low
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Escaping a Sandbox by Calling Code in Another LanguageCAPEC-237likelihood: Low · Very High
- Using Unpublished Interfaces or FunctionalityCAPEC-36likelihood: Medium · High
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.