Skip to content
OpenAdvisories

Weakness (CWE)

CWE-338: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)

Base Draft

The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong.

More detail

When a non-cryptographic PRNG is used in a cryptographic context, it can expose the cryptography to certain types of attacks.

Often a pseudo-random number generator (PRNG) is not designed for cryptography. Sometimes a mediocre source of randomness is sufficient or preferable for algorithms that use random numbers. Weak generators generally take less processing power and/or do not use the precious, finite, entropy sources on a system. While such PRNGs might have very useful features, these same features could be used to break the cryptography.

How to prevent it (1 mitigation)
  1. Implementation

    Use functions or hardware which use a hardware-based random number generation for all crypto. This is the recommended solution. Use CyptGenRandom on Windows, or hw_rand() on Linux.

Source: MITRE CWE-338

55 results · Clear filters · Feed

  • High 8.2

    Cryptographically Weak Generation of One-Time Codes for Identity Verification in ethyca-fides

    Fides is an open-source privacy engineering platform for managing the fulfillment of data privacy requests in a runtime environment, and the enforcement of privacy regulations in code. The Fides Privacy Center allows data subject users to submit privacy and c…

  • High 8.8

    Weak PRNG entropy source used for authentication challenge generation in Motorola MTM5000

    The Motorola MTM5000 series firmwares generate TETRA authentication challenges using a PRNG using a tick count register as its sole entropy source. Low boottime entropy and limited re-seeding of the pool renders the authentication challenge vulnerable to two …

  • High 8.1

    Use of Cryptographically Weak Pseudo-Random Number Generator in Onedev

    Onedev is a self-hosted Git Server with CI/CD and Kanban. In versions prior to 7.9.12 the algorithm used to generate access token and password reset keys was not cryptographically secure. Existing normal users (or everyone if it allows self-registration) may …

  • High 8.8
    CVE-2022-45782 Public exploit

    An issue was discovered in dotCMS core 5.3.8.5 through 5.3.8.15 and 21.03 through 22.10.1. A cryptographically insecure…

  • High 7.4

    Cisco IP Phone Duplicate Key Vulnerability

    A vulnerability in Cisco Unified IP Phones could allow an unauthenticated, remote attacker to impersonate another user's phone if the Cisco Unified Communications Manager (CUCM) is in secure mode. This vulnerability is due to improper key generation during th…

  • High 8.6
    CVE-2021-43799 Public exploit

    RabbitMQ exposes ports with weak default secrets in Zulip Server

    Zulip is an open-source team collaboration tool. Zulip Server installs RabbitMQ for internal message passing. In versions of Zulip Server prior to 4.9, the initial installation (until first reboot, or restart of RabbitMQ) does not successfully limit the defau…

  • High 8.1

    Use of Predictable Algorithm in Random Number Generator in yiisoft/yii2

    yii2 is vulnerable to Use of Predictable Algorithm in Random Number Generator

  • High 7.5

    Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) in star7th/showdoc

    showdoc is vulnerable to Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)

  • High 7.5

    Use of Cryptographically Weak Pseudo-Random Number Generator in Rclone

    An issue was discovered in Rclone before 1.53.3. Due to the use of a weak random number generator, the password generator has been producing weak passwords with much less entropy than advertised. The suggested passwords depend deterministically on the time th…

  • High 8.1

    Use of Insufficiently Random Values in Apereo CAS

    Multiple classes used within Apereo CAS before release 6.1.0-RC5 makes use of apache commons-lang3 RandomStringUtils for token and ID generation which makes them predictable due to RandomStringUtils PRNG's algorithm not being cryptographically strong.

  • High 7.5

    Magento 2 Community Edition Weak PRNG

    A cryptographically weak pseudo-rando number generator is used in multiple security relevant contexts in Magento 2.1 prior to 2.1.18, Magento 2.2 prior to 2.2.9, Magento 2.3 prior to 2.3.2.

  • High 7.5

    matrix-sydent and matrix-synapse Use Cryptographically Weak PRNG

    An issue was discovered in Matrix Sydent before 1.0.3 and Synapse before 0.99.3.1. Random number generation is mishandled, which makes it easier for attackers to predict a Sydent authentication token or a Synapse random ID.

  • High 8.1

    CredHub Service Broker uses guessable client secret

    Pivotal CredHub Service Broker, versions prior to 1.1.0, uses a guessable form of random number generation in creating service broker's UAA client. A remote malicious user may guess the client secret and obtain or modify credentials for users of the CredHub S…

  • High 7.5

    The Bitcoin Proof-of-Work algorithm does not consider a certain attack methodology related to 80-byte block headers wit…

  • High 7.8

    OleumTech WIO Use of Cryptographically Weak Pseudo-Random Number Generator

    OleumTech WIO DH2 Wireless Gateway and Sensor Wireless I/O Modules rely exclusively on a time value for entropy in key generation, which makes it easier for remote attackers to defeat cryptographic protection mechanisms by predicting the time of project creat…