Skip to content
OpenAdvisories

Weakness (CWE)

CWE-341: Predictable from Observable State

Base Draft

A number or object is predictable based on observations that the attacker can make about the state of the system or network, such as time, process ID, etc.

How to prevent it (3 mitigations)
  1. Implementation

    Increase the entropy used to seed a PRNG.

  2. Architecture and Design, Requirements

    Use products or modules that conform to FIPS 140-2 [REF-267] to avoid obvious entropy problems. Consult FIPS 140-2 Annex C ("Approved Random Number Generators").

  3. Implementation

    Use a PRNG that periodically re-seeds itself using input from high-quality sources, such as hardware devices with high entropy. However, do not re-seed too frequently, or else the entropy source might block.

Source: MITRE CWE-341

3 results · Clear filters · Feed

  • Low 3.7

    Apache::AppSamurai::Util versions through 1.01 for Perl generate predictable session authentication keys from the clock and process id in CreateSessionAuthKey

    Apache::AppSamurai::Util versions through 1.01 for Perl generate predictable session authentication keys from the clock and process id in CreateSessionAuthKey. CreateSessionAuthKey runs five rounds of SHA-256, each over a fresh Time::HiRes reading formatted t…

  • Low 3.7

    jsbroks COCO Annotator Session predictable state

    A vulnerability, which was classified as problematic, was found in jsbroks COCO Annotator 0.11.1. This affects an unknown part of the component Session Handler. The manipulation of the argument SECRET_KEY leads to predictable from observable state. It is poss…

  • Low 2.6

    fredsmith utils Filename screenshot_sync predictable state

    A vulnerability, which was classified as problematic, has been found in fredsmith utils. This issue affects some unknown processing of the file screenshot_sync of the component Filename Handler. The manipulation leads to predictable from observable state. The…