Skip to content
Fencer Vulns
high 7.8

CVE-2019-18619 json

Incorrect parameter validation in the synaTee component of Synaptics WBF drivers using an SGX enclave (all versions prior to 2019-11-15) al…

published 2020-07-22 6 y ago modified 2026-06-17 4 mo ago also EUVD-2019-8346

cvss
7.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 44%
public exploits
0
none known

Summary

Incorrect parameter validation in the synaTee component of Synaptics WBF drivers using an SGX enclave (all versions prior to 2019-11-15) allows a local user to execute arbitrary code in the enclave (that can compromise confidentiality of enclave data) via APIs that accept invalid pointers.

Patch / fix

  • lenovo thinkpad_25_firmware 5.2.3540.26
  • lenovo thankpad_a475_firmware 5.02.3539.0026
  • lenovo thankpad_a485_firmware 5.03.3542.0026
  • lenovo thinkpad_e480_firmware 5.2.321.26
  • lenovo thinkpad_e580_firmware 5.2.321.26
  • lenovo thinkpad_e485_firmware 5.2.321.26
  • lenovo thinkpad_e585_firmware 5.2.321.26
  • lenovo thinkpad_e490s_firmware 5.2.321.26
  • lenovo thinkpad_s3_firmware 5.2.321.26
  • lenovo thinkpad_e490_firmware 5.2.321.26
  • lenovo thinkpad_e590_firmware 5.2.321.26
  • lenovo thinkpad_r490_firmware 5.2.321.26
  • lenovo thinkpad_r590_firmware 5.2.321.26
  • lenovo thinkpad_l480_firmware 5.3.3542.26
  • lenovo thinkpad_l580_firmware 5.3.3542.26
  • lenovo thinkpad_p1_firmware 5.3.3542.26
  • lenovo thinkpad_p1_gen_2_firmware 6.0.36.1105
  • lenovo thinkpad_x1_extreme_2nd_firmware 6.0.36.1105
  • lenovo thinkpad_p43s_firmware 6.0.36.1105
  • lenovo thinkpad_p50_firmware 5.1.338.26

Exploit prediction

0.52% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Classification

Weakness
  • CWE-763 Release of Invalid Pointer or Reference

References

Sources

Fencer Vulns 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.