CVE Vulnerabilities

CVE-2019-0007

Use of Insufficiently Random Values

Published: Jan 15, 2019 | Modified: Aug 24, 2020
CVSS 3.x
10
CRITICAL
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CVSS 2.x
7.5 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu

The vMX Series software uses a predictable IP ID Sequence Number. This leaves the system as well as clients connecting through the device susceptible to a family of attacks which rely on the use of predictable IP ID sequence numbers as their base method of attack. This issue was found during internal product security testing. Affected releases are Juniper Networks Junos OS: 15.1 versions prior to 15.1F5 on vMX Series.

Weakness

The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.

Affected Software

Name Vendor Start Version End Version
Junos Juniper 15.1 (including) 15.1 (including)
Junos Juniper 15.1-f1 (including) 15.1-f1 (including)
Junos Juniper 15.1-f2 (including) 15.1-f2 (including)
Junos Juniper 15.1-f3 (including) 15.1-f3 (including)
Junos Juniper 15.1-f4 (including) 15.1-f4 (including)
Junos Juniper 15.1-f5 (including) 15.1-f5 (including)

Potential Mitigations

  • Use a well-vetted algorithm that is currently considered to be strong by experts in the field, and select well-tested implementations with adequate length seeds.
  • In general, if a pseudo-random number generator is not advertised as being cryptographically secure, then it is probably a statistical PRNG and should not be used in security-sensitive contexts.
  • Pseudo-random number generators can produce predictable numbers if the generator is known and the seed can be guessed. A 256-bit seed is a good starting point for producing a “random enough” number.

References