ID CVE-2019-0007
Summary 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.
References
Vulnerable Configurations
  • cpe:2.3:o:juniper:junos:15.1:*:*:*:*:*:*:*
    cpe:2.3:o:juniper:junos:15.1:*:*:*:*:*:*:*
  • cpe:2.3:o:juniper:junos:15.1:f1:*:*:*:*:*:*
    cpe:2.3:o:juniper:junos:15.1:f1:*:*:*:*:*:*
  • cpe:2.3:o:juniper:junos:15.1:f2:*:*:*:*:*:*
    cpe:2.3:o:juniper:junos:15.1:f2:*:*:*:*:*:*
  • cpe:2.3:o:juniper:junos:15.1:f3:*:*:*:*:*:*
    cpe:2.3:o:juniper:junos:15.1:f3:*:*:*:*:*:*
  • cpe:2.3:o:juniper:junos:15.1:f4:*:*:*:*:*:*
    cpe:2.3:o:juniper:junos:15.1:f4:*:*:*:*:*:*
  • cpe:2.3:o:juniper:junos:15.1:f5:*:*:*:*:*:*
    cpe:2.3:o:juniper:junos:15.1:f5:*:*:*:*:*:*
  • cpe:2.3:h:juniper:mx10:-:*:*:*:*:*:*:*
    cpe:2.3:h:juniper:mx10:-:*:*:*:*:*:*:*
  • cpe:2.3:h:juniper:mx10003:-:*:*:*:*:*:*:*
    cpe:2.3:h:juniper:mx10003:-:*:*:*:*:*:*:*
  • cpe:2.3:h:juniper:mx10008:-:*:*:*:*:*:*:*
    cpe:2.3:h:juniper:mx10008:-:*:*:*:*:*:*:*
  • cpe:2.3:h:juniper:mx104:-:*:*:*:*:*:*:*
    cpe:2.3:h:juniper:mx104:-:*:*:*:*:*:*:*
  • cpe:2.3:h:juniper:mx150:-:*:*:*:*:*:*:*
    cpe:2.3:h:juniper:mx150:-:*:*:*:*:*:*:*
  • cpe:2.3:h:juniper:mx2008:-:*:*:*:*:*:*:*
    cpe:2.3:h:juniper:mx2008:-:*:*:*:*:*:*:*
  • cpe:2.3:h:juniper:mx2010:-:*:*:*:*:*:*:*
    cpe:2.3:h:juniper:mx2010:-:*:*:*:*:*:*:*
  • cpe:2.3:h:juniper:mx2020:-:*:*:*:*:*:*:*
    cpe:2.3:h:juniper:mx2020:-:*:*:*:*:*:*:*
  • cpe:2.3:h:juniper:mx204:-:*:*:*:*:*:*:*
    cpe:2.3:h:juniper:mx204:-:*:*:*:*:*:*:*
  • cpe:2.3:h:juniper:mx240:-:*:*:*:*:*:*:*
    cpe:2.3:h:juniper:mx240:-:*:*:*:*:*:*:*
  • cpe:2.3:h:juniper:mx40:-:*:*:*:*:*:*:*
    cpe:2.3:h:juniper:mx40:-:*:*:*:*:*:*:*
  • cpe:2.3:h:juniper:mx480:-:*:*:*:*:*:*:*
    cpe:2.3:h:juniper:mx480:-:*:*:*:*:*:*:*
  • cpe:2.3:h:juniper:mx5:-:*:*:*:*:*:*:*
    cpe:2.3:h:juniper:mx5:-:*:*:*:*:*:*:*
  • cpe:2.3:h:juniper:mx80:-:*:*:*:*:*:*:*
    cpe:2.3:h:juniper:mx80:-:*:*:*:*:*:*:*
  • cpe:2.3:h:juniper:mx960:-:*:*:*:*:*:*:*
    cpe:2.3:h:juniper:mx960:-:*:*:*:*:*:*:*
  • cpe:2.3:h:juniper:vmx:-:*:*:*:*:*:*:*
    cpe:2.3:h:juniper:vmx:-:*:*:*:*:*:*:*
CVSS
Base: 7.5 (as of 24-08-2020 - 17:37)
Impact:
Exploitability:
CWE CWE-330
CAPEC
  • Brute Force
    In this attack, some asset (information, functionality, identity, etc.) is protected by a finite secret value. The attacker attempts to gain access to this asset by using trial-and-error to exhaustively explore all the possible secret values in the hope of finding the secret (or a value that is functionally equivalent) that will unlock the asset. Examples of secrets can include, but are not limited to, passwords, encryption keys, database lookup keys, and initial values to one-way functions. The key factor in this attack is the attackers' ability to explore the possible secret space rapidly. This, in turn, is a function of the size of the secret space and the computational power the attacker is able to bring to bear on the problem. If the attacker has modest resources and the secret space is large, the challenge facing the attacker is intractable. While the defender cannot control the resources available to an attacker, they can control the size of the secret space. Creating a large secret space involves selecting one's secret from as large a field of equally likely alternative secrets as possible and ensuring that an attacker is unable to reduce the size of this field using available clues or cryptanalysis. Doing this is more difficult than it sounds since elimination of patterns (which, in turn, would provide an attacker clues that would help them reduce the space of potential secrets) is difficult to do using deterministic machines, such as computers. Assuming a finite secret space, a brute force attack will eventually succeed. The defender must rely on making sure that the time and resources necessary to do so will exceed the value of the information. For example, a secret space that will likely take hundreds of years to explore is likely safe from raw-brute force attacks.
  • Session Credential Falsification through Prediction
    This attack targets predictable session ID in order to gain privileges. The attacker can predict the session ID used during a transaction to perform spoofing and session hijacking.
  • Signature Spoofing by Key Recreation
    An attacker obtains an authoritative or reputable signer's private signature key by exploiting a cryptographic weakness in the signature algorithm or pseudorandom number generation and then uses this key to forge signatures from the original signer to mislead a victim into performing actions that benefit the attacker.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL PARTIAL
cvss-vector via4 AV:N/AC:L/Au:N/C:P/I:P/A:P
refmap via4
bid 106564
confirm https://kb.juniper.net/JSA10903
Last major update 24-08-2020 - 17:37
Published 15-01-2019 - 21:29
Last modified 24-08-2020 - 17:37
Back to Top