Vulnerabilities > Use of Insufficiently Random Values
| DATE | CVE | VULNERABILITY TITLE | RISK |
|---|---|---|---|
| 2019-03-27 | CVE-2019-9863 | Use of Insufficiently Random Values vulnerability in Abus products 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. | 9.8 |
| 2019-03-27 | CVE-2019-5420 | Use of Insufficiently Random Values vulnerability in multiple products A remote code execution vulnerability in development mode Rails <5.2.2.1, <6.0.0.beta3 can allow an attacker to guess the automatically generated development mode secret token. | 9.8 |
| 2019-03-21 | CVE-2019-9898 | Use of Insufficiently Random Values vulnerability in multiple products Potential recycling of random numbers used in cryptography exists within PuTTY before 0.71. | 9.8 |
| 2019-03-21 | CVE-2019-5885 | Use of Insufficiently Random Values vulnerability in multiple products Matrix Synapse before 0.34.0.1, when the macaroon_secret_key authentication parameter is not set, uses a predictable value to derive a secret key and other secrets which could allow remote attackers to impersonate users. | 7.5 |
| 2019-03-06 | CVE-2019-1543 | Use of Insufficiently Random Values vulnerability in Openssl ChaCha20-Poly1305 is an AEAD cipher, and requires a unique nonce input for every encryption operation. | 7.4 |
| 2019-03-05 | CVE-2019-0729 | Use of Insufficiently Random Values vulnerability in Microsoft Java Software Development KIT An Elevation of Privilege vulnerability exists in the way Azure IoT Java SDK generates symmetric keys for encryption, allowing an attacker to predict the randomness of the key, aka 'Azure IoT Java SDK Elevation of Privilege Vulnerability'. | 9.8 |
| 2019-02-28 | CVE-2019-1997 | Use of Insufficiently Random Values vulnerability in Google Android In random_get_bytes of random.c, there is a possible degradation of randomness due to an insecure default value. | 7.5 |
| 2019-02-19 | CVE-2018-20025 | Use of Insufficiently Random Values vulnerability in Codesys products Use of Insufficiently Random Values exists in CODESYS V3 products versions prior V3.5.14.0. | 7.5 |
| 2019-02-18 | CVE-2019-8919 | Use of Insufficiently Random Values vulnerability in Seafile Seadroid The seadroid (aka Seafile Android Client) application through 2.2.13 for Android always uses the same Initialization Vector (IV) with Cipher Block Chaining (CBC) Mode to encrypt private data, making it easier to conduct chosen-plaintext attacks or dictionary attacks. | 7.5 |
| 2019-01-15 | CVE-2019-0007 | Use of Insufficiently Random Values vulnerability in Juniper Junos 15.1 The vMX Series software uses a predictable IP ID Sequence Number. | 10.0 |