Skip to content
Fencer Intel
medium 5.8

CVE-2019-13543 json

Medtronic Valleylab FT10 and FX8 Use of Hard-coded Credentials

published 7y ago modified 4mo ago also EUVD-2019-4998

cvss
5.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.0%
EPSS 2.0% chance of exploitation in 30 days, percentile 81%
public exploits
0
none known

Summary

Medtronic Valleylab Exchange Client version 3.4 and below, Valleylab FT10 Energy Platform (VLFT10GEN) software version 4.0.0 and below, and Valleylab FX8 Energy Platform (VLFX8GEN) software version 1.1.0 and below use multiple sets of hard-coded credentials. If discovered, they can be used to read files on the device.

Is CVE-2019-13543 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-19-311-02 updated cvss 5.8

Medtronic Valleylab FT10 and FX8

  • Medtronic Valleylab Exchange Client <= 3.4 Medtronic Valleylab FT10 Energy Platform (VLFT10GEN) software <= 4.0.0 Medtronic Valleylab FX8 Energy Platform (VLFX8GEN) software <= 1.0.0
    affected: vendor fix medtronic.com

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

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

CVSS scores

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

Affected products

  • Medtronic Valleylab Exchange Client
  • Medtronic Valleylab FT10 Energy Platform (VLFT10GEN)
  • Medtronic Valleylab FX8 Energy Platform (VLFX8GEN)

Classification

Weakness
  • CWE-798 Use of Hard-coded Credentials

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.