IDCVSSSummaryLast (major) updatePublished
CVE-2019-14261 5.0
An issue was discovered on ABUS Secvest FUAA50000 3.01.01 devices. Due to an insufficient implementation of jamming detection, an attacker is able to suppress correctly received RF messages sent between wireless peripheral components, e.g., wireless
05-09-2019 - 20:37 03-09-2019 - 18:15
CVE-2019-9861 4.8
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.
17-05-2019 - 12:58 14-05-2019 - 17:29
CVE-2019-9862 3.3
An issue was discovered on ABUS Secvest wireless alarm system FUAA50000 3.01.01 in conjunction with Secvest remote control FUBE50014 or FUBE50015. Because "encrypted signal transmission" is missing, an attacker is able to eavesdrop sensitive data as
24-08-2020 - 17:37 27-03-2019 - 14:29
CVE-2019-9860 5.0
Due to unencrypted signal communication and predictability of rolling codes, an attacker can "desynchronize" an ABUS Secvest wireless remote control (FUBE50014 or FUBE50015) relative to its controlled Secvest wireless alarm system FUAA50000 3.01.01,
21-07-2021 - 11:39 27-03-2019 - 15:29
CVE-2019-9863 10.0
Due to the use of an insecure algorithm for rolling codes in the ABUS Secvest wireless alarm system FUAA50000 3.01.01 and its remote controls FUBE50014 and FUBE50015, an attacker is able to predict valid future rolling codes, and can thus remotely co
21-07-2021 - 11:39 27-03-2019 - 14:29
CVE-2020-28973 5.0
The ABUS Secvest wireless alarm system FUAA50000 (v3.01.17) fails to properly authenticate some requests to its built-in HTTPS interface. Someone can use this vulnerability to obtain sensitive information from the system, such as usernames and passwo
27-04-2021 - 19:42 21-04-2021 - 19:15
Back to Top Mark selected
Back to Top