CVE-2019-9861 json
Due to the use of an insecure RFID technology (MIFARE Classic), ABUS proximity chip keys (RFID tokens) of the ABUS Secvest FUAA50000 wirele…
published 7y ago modified 4mo ago also EUVD-2019-19217
- cvss
- 8.1
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
Due to the use of an insecure RFID technology (MIFARE Classic), ABUS proximity chip keys (RFID tokens) of the ABUS Secvest FUAA50000 wireless alarm system can easily be cloned and used to deactivate the alarm system in an unauthorized way.
Is CVE-2019-9861 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.59% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- syss.de https://www.syss.de/fileadmin/dokumente/Publikationen/Advisories/SYSS-2019-005.txt referenced PoC, tagged "exploit" by a source, unverified
- seclists.org https://seclists.org/bugtraq/2019/May/1 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.com http://packetstormsecurity.com/files/152714/ABUS-Secvest-3.01.01-Cryptographic-Issues.html referenced PoC, tagged "exploit" by a source, unverified
- seclists.org http://seclists.org/fulldisclosure/2019/May/3 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.1 | CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| NVD | 2.0 | 4.8 | AV:A/AC:L/Au:N/C:P/I:P/A:N |
Classification
- Weakness
-
- CWE-310 Cryptographic Issues
References
-
syss.de
/fileadmin/dokumente/Publikationen/Advisories/SYSS-2019-005.txt
exploit, third-party-advisory
-
seclists.org
/bugtraq/2019/May/1
mailing-list, exploit, third-party-advisory
-
packetstormsecurity.com
/files/152714/ABUS-Secvest-3.01.01-Cryptographic-Issues.html
exploit, third-party-advisory, vdb-entry
-
seclists.org
/fulldisclosure/2019/May/3
mailing-list, exploit, third-party-advisory
Sources
- CVE List CVE-2019-9861
- NVD CVE-2019-9861
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.