CVE-2019-18201 json
An issue was discovered on Fujitsu Wireless Keyboard Set LX390 GK381 devices.
published 7y ago modified 4mo ago also EUVD-2019-8003
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 69%
- public exploits
- 0
- none known
Summary
An issue was discovered on Fujitsu Wireless Keyboard Set LX390 GK381 devices. Because of the lack of proper encryption of 2.4 GHz communication, an attacker is able to eavesdrop on sensitive data such as passwords.
Is CVE-2019-18201 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 FencerExploit prediction
1.23% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- syss.de https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2019-010.txt referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/154955/Fujitsu-Wireless-Keyboard-Set-LX390-Missing-Encryption.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| 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 |
Classification
- Weakness
-
- CWE-319 Cleartext Transmission of Sensitive Information
References
-
syss.de
/fileadmin/dokumente/Publikationen/Advisories/SYSS-2019-010.txt
exploit, third-party-advisory
-
packetstormsecurity.com
/files/154955/Fujitsu-Wireless-Keyboard-Set-LX390-Missing-Encryption.html
exploit, third-party-advisory, vdb-entry
-
syss.de
/pentest-blog/2019/syss-2019-009-syss-2019-010-und-syss-2019-011-schwachstellen-in-weiterer-funktastatur-mit-s
third-party-advisory
Sources
- CVE List CVE-2019-18201
- NVD CVE-2019-18201
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.