Medtronic Vulnerabilities

Timeline

The analysis of the timeline helps to identify the required approach and handling of single vulnerabilities and vulnerability collections. This overview makes it possible to see less important slices and more severe hotspots at a glance. Initiating immediate vulnerability response and prioritizing of issues is possible.

Type

The moderation team is working with the threat intelligence team to categorize software that is affected by security vulnerabilities. This helps to illustrate the assignment of these categories to determine the most affected software types.

Product

Medtronic Valleylab FT10 Energy Platform4
Medtronic Smart Model 25000 Patient Reader3
Medtronic CareLink 2090 Programmer3
Medtronic 2090 Carelink Programmer3
Medtronic Valleylab Exchange Client2

Grouping vulnerabilities by products helps to get an overview. This makes it possible to determine an homogeneous landscape or the most important hotspots in heterogeneous landscapes.

Remediation

Official Fix4
Temporary Fix0
Workaround1
Unavailable1
Not Defined20

Vendors and researchers are eager to find countermeasures to mitigate security vulnerabilities. These can be distinguished between multiple forms and levels of remediation which influence risks differently.

Exploitability

High0
Functional0
Proof-of-Concept0
Unproven1
Not Defined25

Researcher and attacker which are looking for security vulnerabilities try to exploit them for academic purposes or personal gain. The level and quality of exploitability can be distinguished to determine simplicity and strength of attacks.

Access Vector

Not Defined0
Physical11
Local4
Adjacent6
Network5

The approach a vulnerability it becomes important to use the expected access vector. This is typically via the network, local, or physically even.

Authentication

Not Defined0
High0
Low4
None22

To exploit a vulnerability a certail level of authentication might be required. Vulnerabilities without such a requirement are much more popular.

User Interaction

Not Defined0
Required3
None23

Some attack scenarios require some user interaction by a victim. This is typical for phishing, social engineering and cross site scripting attacks.

C3BM Index

Our unique C3BM Index (CVSSv3 Base Meta Index) cumulates the CVSSv3 Meta Base Scores of all entries over time. Comparing this index to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

CVSSv3 Base

≤10
≤20
≤31
≤41
≤57
≤69
≤73
≤82
≤91
≤102

The Common Vulnerability Scoring System (CVSS) is an industry standard to define the characteristics and impacts of security vulnerabilities. The base score represents the intrinsic aspects that are constant over time and across user environments. Our unique meta score merges all available scores from different sources to aggregate to the most reliable result.

CVSSv3 Temp

≤10
≤20
≤31
≤41
≤57
≤69
≤73
≤82
≤91
≤102

The Common Vulnerability Scoring System (CVSS) uses temp scores to reflect the characteristics of a vulnerability that may change over time but not across user environments. This includes reporting confidence, exploitability and remediation levels. We do also provide our unique meta score for temp scores, even though other sources rarely publish them.

VulDB

≤10
≤20
≤32
≤43
≤512
≤63
≤70
≤83
≤91
≤102

The moderation team is always defining the base vector and base score for an entry. These and all other available scores are used to generate the meta score.

NVD

≤10
≤20
≤30
≤40
≤55
≤64
≤76
≤84
≤92
≤100

The National Vulnerability Database (NVD) is also defining CVSS vectors and scores. These are usually not complete and might differ from VulDB scores.

CNA

≤10
≤20
≤30
≤40
≤50
≤60
≤71
≤80
≤90
≤101

A CVE Numbering Authority (CNA) is responsible for assigning new CVE entries. They might also include a CVSS score. These are usually not complete and might differ from VulDB scores.

Vendor

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

Some vendors are willing to publish their own CVSS vectors and scores for vulnerabilities in their products. The coverage varies from vendor to vendor.

Research

≤10
≤20
≤30
≤40
≤50
≤60
≤70
≤80
≤90
≤100

There are sometimes also security researcher which provide their own CVSS vectors and scores for vulnerabilities they have found and published.

Exploit 0-day

<1k13
<2k9
<5k2
<10k0
<25k1
<50k1
<100k0
≥100k0

The moderation team is working with the threat intelligence team to determine prices for exploits. Our unique algorithm is used to identify the 0-day prices for an exploit, before it got distributed or became public. Calculated prices are aligned to prices disclosed by vulnerability broker and compared to prices we see on exploit markets.

Exploit Today

<1k23
<2k1
<5k1
<10k0
<25k0
<50k1
<100k0
≥100k0

The 0-day prices do not consider time-relevant factors. The today price does reflect price impacts like disclosure of vulnerability details, alternative exploits, availability of countermeasures. These dynamic aspects might decrease the exploit prices over time. Under certain circumstances this happens very fast.

Exploit Market Volume

Our unique calculation of exploit prices makes it possible to forecast the expected exploit market volume. The calculated prices for all possible 0-day expoits are cumulated for this task. Comparing the volume to the amount of disclosed vulnerabilities helps to pinpoint the most important events.

🔴 CTI Activities

Our unique Cyber Threat Intelligence aims to determine the ongoing research of actors to anticipiate their acitivities. Observing exploit markets on the Darknet, discussions of vulnerabilities on mailinglists, and exchanges on social media makes it possible to identify planned attacks. Monitored actors and activities are classified whether they are offensive or defensive. They are also weighted as some actors are well-known for certain products and technologies. And some of their disclosures might contain more or less details about technical aspects and personal context. The world map highlights active actors in real-time.

Affected Products (60): 2090 Carelink Programmer (3), 8840 N'Vision Clinician Programmer (2), 8870 N'Vision Removable Application Card (2), 24950 MyCareLink Monitor (2), 24952 MyCareLink Monitor (2), Amplia CRT-D (2), CareLink 2090 Programmer (3), CareLink 9790 Programmer 29901 (1), CareLink Monitor (2), Claria CRT-D (2), Compia CRT-D (2), Concerto CRT-D (2), Consulta CRT-D (2), Evera ICD (2), InsterStim Applications (1), MMT 508 (2), MMT 522 (2), MMT 523 (2), MMT 523K (2), MMT 530G (2), MMT 551 (2), MMT 722 (2), MMT 723 (2), MMT 723K (2), MMT 751 (2), Maximo II CRT-D (2), Maximo II ICD (2), MinMed 508 (1), MiniMed 620G (1), MiniMed 630G (1), MiniMed 640G (1), MiniMed 670G (1), MiniMed Paradigm 515 (1), MiniMed Paradigm 522 (1), MiniMed Paradigm 522K (1), MiniMed Paradigm 523 (1), MiniMed Paradigm 712E (1), MiniMed Paradigm 715 (1), MiniMed Paradigm 722 (1), MiniMed Paradigm 722K (1), MiniMed Paradigm 723 (1), Minimed Paradigm 512 (1), Minimed Paradigm 712 (1), Mirro ICD (2), MyCareLink 24950 (2), MyCareLink 24952 (2), MyCareLink Monitor (2), MyCareLink Patient Monitor (2), Nayamed ND ICD (2), Paceart Optima (1), Paradigm wireless insulin pump (1), Primo ICD (2), Protecta CRT-D (2), Protecta ICD (2), Secura ICD (2), Smart Model 25000 Patient Reader (3), Valleylab Exchange Client (2), Valleylab FT10 Energy Platform (4), Valleylab FX8 Energy Platform (2), Valleylab LS10 Energy Platform (2)

PublishedBaseTempVulnerabilityProdExpRemEPSSCTICVE
06/29/20239.59.5Medtronic Paceart Optima Microsoft Messaging Queuing Service deserializationUnknownNot DefinedNot Defined0.000530.03CVE-2023-31222
03/01/20235.85.8Medtronic InsterStim Applications unverified password changeUnknownNot DefinedOfficial Fix0.000540.00CVE-2023-25931
09/24/20222.92.9Medtronic MiniMed 620G protection mechanismUnknownNot DefinedWorkaround0.000420.04CVE-2022-32537
12/13/20209.69.2Medtronic Smart Model 25000 Patient Reader Update System toctouMedical Device SoftwareNot DefinedOfficial Fix0.003120.00CVE-2020-27252
12/13/20208.88.4Medtronic Smart Model 25000 Patient Reader Debug Command heap-based overflowMedical Device SoftwareNot DefinedOfficial Fix0.005440.00CVE-2020-25187
12/13/20205.55.3Medtronic Smart Model 25000 Patient Reader App Authentication improper authenticationMedical Device SoftwareNot DefinedOfficial Fix0.000650.00CVE-2020-25183
11/08/20197.47.4Medtronic Valleylab Exchange Client hard-coded credentialsMedical Device SoftwareNot DefinedNot Defined0.001620.03CVE-2019-13543
11/08/20195.55.5Medtronic Valleylab Exchange Client Password Hashing input validationMedical Device SoftwareNot DefinedNot Defined0.000440.02CVE-2019-13539
11/08/20193.33.3Medtronic Valleylab LS10 Energy Platform RFID protection mechanismMedical Device SoftwareNot DefinedNot Defined0.000670.00CVE-2019-13535
11/08/20194.44.4Medtronic Valleylab LS10 Energy Platform RFID improper authenticationMedical Device SoftwareNot DefinedNot Defined0.000550.00CVE-2019-13531

16 more entries are not shown

Do you want to use VulDB in your project?

Use the official API to access entries easily!