1197 matches found
CVE-2020-11616
NVIDIA DGX servers, all BMC firmware versions prior to 3.38.30, contain a vulnerability in the AMI BMC firmware in which the Pseudo-Random Number Generator PRNG algorithm used in the JSOL package that implements the IPMI protocol is not cryptographically strong, which may lead to information...
Information disclosure
NVIDIA DGX servers, all BMC firmware versions prior to 3.38.30, contain a vulnerability in the AMI BMC firmware in which the Pseudo-Random Number Generator PRNG algorithm used in the JSOL package that implements the IPMI protocol is not cryptographically strong, which may lead to information...
CVE-2020-11616
CVE-2020-11616 affects NVIDIA DGX servers with BMC firmware versions prior to 3.38.30. The vulnerability arises from a weak PRNG in the JSOL IPMI package of the AMI BMC firmware, which could lead to information disclosure. Public documents identify the affected product class but do not provide ex...
CVE-2020-11616
NVIDIA DGX servers, all BMC firmware versions prior to 3.38.30, contain a vulnerability in the AMI BMC firmware in which the Pseudo-Random Number Generator PRNG algorithm used in the JSOL package that implements the IPMI protocol is not cryptographically strong, which may lead to information...
PT-2020-12729
Name of the Vulnerable Software and Affected Versions NVIDIA DGX servers versions prior to 3.38.30 Description The issue is related to a weakness in the Pseudo-Random Number Generator PRNG algorithm used in the JSOL package, which implements the IPMI protocol in the AMI BMC firmware. This weaknes...
CVE-2020-11616: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
NVIDIA DGX servers, all BMC firmware versions prior to 3.38.30, contain a vulnerability in the AMI BMC firmware in which the Pseudo-Random Number Generator PRNG algorithm used in the JSOL package that implements the IPMI protocol is not cryptographically strong, which may lead to information...
Security Bulletin: IBM BigInsights is affected by multiple vulnerabilities in IBM Db2
Summary IBM BigInsights is affected by multiple vulnerabilities in IBM Db2. Vulnerability Details CVEID: CVE-2016-0702 DESCRIPTION: OpenSSL could allow a local attacker to obtain sensitive information, caused by a side-channel attack against a system based on the Intel Sandy-Bridge...
JHipster Kotlin using insecure source of randomness `RandomStringUtils` before v1.2.0
JHipster Kotlin is using an insecure source of randomness to generate all of its random values. JHipster Kotlin relies upon apache commons lang3 RandomStringUtils. From the documentation: Caveat: Instances of Random, upon which the implementation of this class relies, are not cryptographically...
CVE-2020-13784
D-Link DIR-865L Ax 1.20B01 Beta devices have a predictable seed in a Pseudo-Random Number Generator...
Code injection
D-Link DIR-865L Ax 1.20B01 Beta devices have a predictable seed in a Pseudo-Random Number Generator...
CVE-2020-13784
CVE-2020-13784 concerns the D-Link DIR-865L Ax router with firmware 1.20B01 Beta, where the pseudo-random number generator uses a predictable seed. The connected CNVD entry confirms a security feature issue vulnerability for the same device/firmware, citing the easily guessable PRNG seed as the u...
PT-2020-2912
Name of the Vulnerable Software and Affected Versions D-Link DIR-865L Ax version 1.20B01 Beta Description The issue is related to a predictable seed in a Pseudo-Random Number Generator, specifically in the get random string function of the D-Link DIR-865L router's firmware. This is caused by erro...
CVE-2020-6616
Some Broadcom chips mishandle Bluetooth random-number generation because a low-entropy Pseudo Random Number Generator PRNG is used in situations where a Hardware Random Number Generator HRNG should have been used to prevent spoofing. This affects, for example, Samsung Galaxy S8, S8+, and Note8...
CVE-2020-6616
Some Broadcom chips mishandle Bluetooth random-number generation because a low-entropy Pseudo Random Number Generator PRNG is used in situations where a Hardware Random Number Generator HRNG should have been used to prevent spoofing. This affects, for example, Samsung Galaxy S8, S8+, and Note8...
CVE-2020-6616: Undefined Security Weakness
Some Broadcom chips mishandle Bluetooth random-number generation because a low-entropy Pseudo Random Number Generator PRNG is used in situations where a Hardware Random Number Generator HRNG should have been used to prevent spoofing. This affects, for example, Samsung Galaxy S8, S8+, and Note8...
Information Disclosure
ruby is vulnerable to information disclosure. It was found that Ruby did not reinitialize the PRNG pseudorandom number generator after forking a child process. This could eventually lead to the PRNG returning the same result twice. An attacker keeping track of the values returned by one child...
Information Leakage
Ruby is vulnerable to information leakage. The attack is possible due to a flaw in the Ruby SecureRandom module. When using the SecureRandom.randombytes class, the PRNG state was not modified after forking a child process. This could eventually lead to SecureRandom.randombytes returning the same...
CVE-2020-10560: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
An issue was discovered in Open Source Social Network OSSN through 5.3. A user-controlled file path with a weak cryptographic rand can be used to read any file with the permissions of the webserver. This can lead to further compromise. The attacker must conduct a brute-force attack against the...
Exploit for Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) in Opensource-Socialnetwork Open_Source_Social_Network
CVE-2020-10560 CVE-2020-10560 OSSN Arbitrary File Read For de...
Epignosis eFront LMS Password Reset authentication bypass vulnerability
Summary A predictable seed vulnerability eixsts in the password reset functionality of Epignosis EfrontPro 5.2.21. By predicting the seed it is possible to generate the correct password reset 1-time token. An attacker can visit the password reset supplying the password reset token to reset the...