1100 matches found
CVE-2019-9863
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 control the alarm system in an unauthorized way...
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-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-9863
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 control the alarm system in an unauthorized way...
Design/Logic Flaw
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
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...
CVE-2019-9862
The CVE-2019-9862 entry concerns ABUS Secvest wireless alarm system FUAA50000 (version 3.01.01) when used with Secvest remote controls FUBE50014/FUBE50015. The root cause is the lack of encrypted signal transmission, which allows an attacker to eavesdrop sensitive data in cleartext (for example, ...
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-9863
CVE-2019-9863 concerns the ABUS Secvest wireless alarm system FUAA50000 (v3.01.01) and its remote controls FUBE50014/FUBE50015. The root cause is an insecure algorithm used for rolling codes, which enables an attacker to predict valid future rolling codes and remotely control the alarm system in ...
CVE-2019-9862: Missing Encryption of Sensitive Data
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...
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...
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...
CVE-2014-5431
Baxter SIGMA Spectrum Infusion System version 6.05 model 35700BAX with wireless battery module WBM version 16 contains a hard-coded password, which provides access to basic biomedical information, limited device settings, and network configuration of the WBM, if connected. The hard-coded password...
Design/Logic Flaw
The Chuango 433 MHz burglar-alarm product line uses static codes in the RF remote control, allowing an attacker to arm, disarm, or trigger the alarm remotely via replay attacks, as demonstrated by Chuango branded products, and non-Chuango branded products such as the Eminent EM8617 OV2 Wifi Alarm...
CVE-2019-9659
The Chuango 433 MHz burglar-alarm product line uses static codes in the RF remote control, allowing an attacker to arm, disarm, or trigger the alarm remotely via replay attacks, as demonstrated by Chuango branded products, and non-Chuango branded products such as the Eminent EM8617 OV2 Wifi Alarm...
CVE-2019-9659
CVE-2019-9659 affects the Chuango 433 MHz burglar-alarm product line, where static RF remote codes enable replay-based arming, disarming, or triggering the alarm. The NVD description confirms the vulnerability stems from fixed code sequences used by the remote controls, allowing an attacker to re...
CVE-2019-9659
The Chuango 433 MHz burglar-alarm product line uses static codes in the RF remote control, allowing an attacker to arm, disarm, or trigger the alarm remotely via replay attacks, as demonstrated by Chuango branded products, and non-Chuango branded products such as the Eminent EM8617 OV2 Wifi Alarm...
CVE-2019-9659: Authentication Bypass by Capture-replay
The Chuango 433 MHz burglar-alarm product line uses static codes in the RF remote control, allowing an attacker to arm, disarm, or trigger the alarm remotely via replay attacks, as demonstrated by Chuango branded products, and non-Chuango branded products such as the Eminent EM8617 OV2 Wifi Alarm...
PT-2019-19783
Name of the Vulnerable Software and Affected Versions Chuango 433 MHz burglar-alarm product line affected versions not specified Eminent EM8617 OV2 Wifi Alarm System affected versions not specified Description The issue concerns the use of static codes in the RF remote control of the affected...
The Latest in Creepy Spyware
The Nest home alarm system shipped with a secret microphone, which -- according to the company -- was only an accidental secret: On Tuesday, a Google spokesperson told Business Insider the company had made an "error." "The on-device microphone was never intended to be a secret and should have bee...