CVE-2020-28973

The ABUS Secvest FUAA50000 system (v3.01.17) contains an authentication flaw in its built‑in HTTPS interface that can disclose sensitive credentials (e.g., usernames and passwords). An attacker can use this to reconfigure or disable the alarm system. The root cause is described as improper authen...

CVE-2020-28973: Improper Authentication

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 passwords. This information can then be used to...

ABUS Secvest FUAA50000 information leakage vulnerability

ABUS Secvest FUAA50000 is a wireless remote control from ABUS Germany. An information disclosure vulnerability exists in ABUS Secvest FUAA50000 version 3.01.17, which can be exploited by an attacker to obtain sensitive information, such as usernames and passwords, from the system...

Design/Logic Flaw

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 detectors or remote controls, and the ABUS...

CVE-2019-14261

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 detectors or remote controls, and the ABUS...

CVE-2019-14261

CVE-2019-14261 affects ABUS Secvest FUAA50000 (firmware 3.01.01). The issue is an insufficient jamming-detection implementation allowing reactive jamming: an attacker detects the start of a wireless RF message (e.g., from a detector like FUBW50000 or a remote such as FUBE50014/15) and overlays it...

CVE-2019-14261: Undefined Security Weakness

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 detectors or remote controls, and the ABUS...

PT-2019-13569

Name of the Vulnerable Software and Affected Versions ABUS Secvest FUAA50000 version 3.01.01 Description An issue was discovered due to an insufficient implementation of jamming detection. This allows an attacker to suppress correctly received RF messages sent between wireless peripheral componen...

CVE-2019-9861

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

CVE-2019-9861

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

Design/Logic Flaw

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

CVE-2019-9861

The CVE-2019-9861 entry concerns ABUS Secvest FUAA50000 wireless alarm system: an insecure RFID technology (MIFARE Classic) allows cloning of proximity chip keys (RFID tokens) and unauthorized deactivation of the alarm. Affected component is the RFID-based access mechanism used by ABUS proximity ...

PT-2019-19896

Name of the Vulnerable Software and Affected Versions ABUS Secvest FUAA50000 wireless alarm system affected versions not specified Description The issue is related to the use of insecure RFID technology, specifically MIFARE Classic, in ABUS proximity chip keys. This allows the keys to be easily...

CVE-2019-9861: Undefined Security Weakness

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

CVE-2019-9860

CVE-2019-9860 maps to ABUS Secvest legacy system components: wireless remote controls FUBE50014/FUBE50015 and the FUAA50000 3.01.01 alarm, with a root cause of unencrypted signal communication and easily guessable rolling codes. This allows an attacker to desynchronize the remote from the alarm, ...

CVE-2019-9862

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 cleartext for instance, the current rolling cod...

CVE-2019-9860: Cleartext Transmission of Sensitive Information

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, so that sent commands by the remote control are n...

PT-2019-19895

Name of the Vulnerable Software and Affected Versions ABUS Secvest wireless alarm system FUAA50000 version 3.01.01 ABUS Secvest wireless remote control versions FUBE50014 or FUBE50015 Description The issue arises from unencrypted signal communication and the predictability of rolling codes in the...

PT-2019-19898

Name of the Vulnerable Software and Affected Versions ABUS Secvest wireless alarm system FUAA50000 version 3.01.01 ABUS Secvest remote controls FUBE50014 affected versions not specified ABUS Secvest remote controls FUBE50015 affected versions not specified Description The issue arises from the us...

PT-2019-19897

Name of the Vulnerable Software and Affected Versions ABUS Secvest wireless alarm system FUAA50000 version 3.01.01 Description An issue was discovered where sensitive data, such as the current rolling code state, is transmitted in cleartext due to the lack of "encrypted signal transmission". This...