Home/CVE/Medtronic Valleylab Exchange Client version 3.4 and below, Valleylab FT10 Energy Platform (VLFT10GEN) software version 4
CVE
CVE-2019-13539
Medtronic Valleylab Exchange Client version 3.4 and below, Valleylab FT10 Energy Platform (VLFT10GEN) software version 4
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 the descrypt algorithm for OS password hashing. While interactive, network-based logons are disabled, and attackers can use the other vulnerabilities within this report to obtain local shell access and access these hashes.
HIGH · CVSS 7
EPSS 0.00268
EPSS exploitation odds0.27% · top 81%
Schedule remediation
- CVSS base score ≥ 7.0
No Sigma yet — build one →
YARA rules0
Look this up elsewhere - one-click external pivots
▸
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2019-13539, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked.
EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal.
CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score.
Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits.
PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).
EPSS exploitation probability
0.27%
Top 81%odds of exploitation in the next 30 days
CVSS metric silhouette
shape grows toward worst-case
SSVC triage
No SSVC vulnrichment for this CVE. CISA's Vulnrichment program scores newer CVEs (~2024 onwards) plus selected older critical ones. Use the EPSS probability + KEV status to triage instead.
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network
Adjacent
Local
Physical
Attack Complexity
Low
High
Privileges Required
None
Low
High
User Interaction
None
Required
Scope
Unchanged
Changed
Impact - what breaks
Confidentiality
None
Low
High
Integrity
None
Low
High
Availability
None
Low
High
VECTOR
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:HLifecycle
- 08 Nov 2019Published to NVD
- 17 Jun 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain
◆
ATT&CK techniques
2Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small N× marks a technique that N independent sources agree on.
▤ Build a SIEM detection for these techniques▤
CAPEC attack patterns
5Attack patterns this CVE enables - the bridge from weakness to ATT&CK technique.
⬡
Weakness Classification
CWE-328Use of Weak Hash
▤
Affected Products & Versions
3▤
Related CVEs
8CVEs linked to this one by a shared weakness (CWE) or affected product - joins on data already in the engine, with the reason shown per row. Not a guess.
CVE-2001-1546
Pathways Homecare 6.5 uses weak encryption for user names and passwords, which a...
1
same CWE-326
HIGH
CVE-2002-1682
NewsReactor 1.0 uses a weak encryption scheme, which could allow local users to ...
same CWE-326
MEDIUM
CVE-2002-1697
Electronic Code Book (ECB) mode in VTun 2.0 through 2.5 uses a weak encryption a...
same CWE-326
HIGH
CVE-2002-1739
Alt-N Technologies Mdaemon 5.0 through 5.0.6 uses a weak encryption algorithm to...
same CWE-326
MEDIUM
CVE-2020-37168
Ecommerce Systempay 1.0 contains a weak cryptographic implementation vulnerabili...
same CWE-328
CRITICAL
CVE-2021-39182
EnroCrypt is a Python module for encryption and hashing. Prior to version 1.1.4,...
same CWE-328
HIGH
CVE-2022-29249
JavaEZ is a library that adds new functions to make Java easier. A weakness in J...
same CWE-328
HIGH
CVE-2022-29835
WD Discovery software executable files were signed with an unsafe SHA-1 hashing ...
same CWE-328
MEDIUM
⚑
Vendor Advisories
1cisa-csafcisa-csaf-csaf_files-OT-white-2019-icsma-19-311-02
🔗
References & Sources
3Source URLs (vendor pages, mailing lists, write-ups). Exploit/PoC links are in their own section above to avoid duplication.