ABUS Secvest Wireless Alarm System FUAA50000 3.01.01 Desynchronize entropy
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in ABUS Secvest Wireless Alarm System FUAA50000 3.01.01. It has been classified as problematic. The impacted element is an unknown function. The manipulation leads to entropy (Desynchronize). This vulnerability is uniquely identified as CVE-2019-9860. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in ABUS Secvest Wireless Alarm System FUAA50000 3.01.01 and classified as problematic. This issue affects an unknown code block. The manipulation with an unknown input leads to a entropy vulnerability (Desynchronize). Using CWE to declare the problem leads to CWE-332. The lack of entropy available for, or used by, a Pseudo-Random Number Generator (PRNG) can be a stability and security threat. Impacted is availability. The summary by CVE is:
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 not accepted anymore.
The bug was discovered 03/25/2019. The weakness was disclosed 03/27/2019. The identification of this vulnerability is CVE-2019-9860 since 03/18/2019. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1600.001 for this issue.
The vulnerability was handled as a non-public zero-day exploit for at least 2 days. During that time the estimated underground price was around $0-$5k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-132559 and VDB-132558 are pretty similar. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Name: DesynchronizeClass: Entropy / Desynchronize
CWE: CWE-332 / CWE-331 / CWE-330
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
03/18/2019 🔍03/25/2019 🔍
03/27/2019 🔍
03/28/2019 🔍
08/17/2023 🔍
Sources
Advisory: syss.deStatus: Not defined
CVE: CVE-2019-9860 (🔍)
GCVE (CVE): GCVE-0-2019-9860
GCVE (VulDB): GCVE-100-132557
See also: 🔍
Entry
Created: 03/28/2019 14:25Updated: 08/17/2023 12:41
Changes: 03/28/2019 14:25 (54), 05/22/2020 15:17 (1), 08/17/2023 12:41 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.