CVE Vulnerabilities

CVE-2015-3963

Use of Insufficiently Random Values

Published: Aug 04, 2015 | Modified: Jul 22, 2021
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
5.8 MEDIUM
AV:N/AC:M/Au:N/C:N/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu

Wind River VxWorks before 5.5.1, 6.5.x through 6.7.x before 6.7.1.1, 6.8.x before 6.8.3, 6.9.x before 6.9.4.4, and 7.x before 7 ipnet_coreip 1.2.2.0, as used on Schneider Electric SAGE RTU devices before J2 and other devices, does not properly generate TCP initial sequence number (ISN) values, which makes it easier for remote attackers to spoof TCP sessions by predicting an ISN value.

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
Vxworks Windriver 6.5 (including) 6.6 (including)
Vxworks Windriver 6.7 (including) 6.7.1.1 (excluding)
Vxworks Windriver 6.8 (including) 6.8.3 (excluding)
Vxworks Windriver 6.9 (including) 6.9.4.4 (excluding)
Vxworks Windriver 6.6.3 (including) 6.6.3 (including)
Vxworks Windriver 6.6.4 (including) 6.6.4 (including)
Vxworks Windriver 6.6.4.1 (including) 6.6.4.1 (including)
Vxworks Windriver 7.0 (including) 7.0 (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