CVE-2020-1653

Vulnérabilité élevée dans Junos OS (Juniper Networks)

CVSS 7.5 · Élevée
EPSS 1.6%
Juniper Networks•Junos OS•Versions : <17.4R1, <18.1R3-S10, 19.2, 19.3, 18.2, <18.3R2-S4, 18.3R3-S2, <17.4R2-S11, 17.4R3-S2, 18.3, 19.1, <19.3R2-S3, 19.3R3, 18.1, 17.4, 18.4, <19.2R1-S5, 19.2R2, 19.4, <18.4R1-S7, 18.4R2-S4, 18.4R3-S1, 18.2X75, <18.2X75-D41, 18.2X75-D420.12, 18.2X75-D51, 18.2X75-D60, 18.2X75-D34, <19.1R1-S5, 19.1R2-S1, 19.1R3, <18.2R2-S7, 18.2R3-S5, <19.4R1-S2, 19.4R2

Description

On Juniper Networks Junos OS devices, a stream of TCP packets sent to the Routing Engine (RE) may cause mbuf leak which can lead to Flexible PIC Concentrator (FPC) crash or the system to crash and restart (vmcore). This issue can be trigged by IPv4 or IPv6 and it is caused only by TCP packets. This issue is not related to any specific configuration and it affects Junos OS releases starting from 17.4R1. However, this issue does not affect Junos OS releases prior to 18.2R1 when Nonstop active routing (NSR) is configured [edit routing-options nonstop-routing]. The number of mbufs is platform dependent. The following command provides the number of mbufs counter that are currently in use and maximum number of mbufs that can be allocated on a platform: user@host> show system buffers 2437/3143/5580 mbufs in use (current/cache/total) Once the device runs out of mbufs, the FPC crashes or the vmcore occurs and the device might become inaccessible requiring a manual restart. This issue affects Juniper Networks Junos OS 17.4 versions prior to 17.4R2-S11, 17.4R3-S2; 18.1 versions prior to 18.1R3-S10; 18.2 versions prior to 18.2R2-S7, 18.2R3-S5; 18.2X75 versions prior to 18.2X75-D41, 18.2X75-D420.12, 18.2X75-D51, 18.2X75-D60, 18.2X75-D34; 18.3 versions prior to 18.3R2-S4, 18.3R3-S2; 18.4 versions prior to 18.4R1-S7, 18.4R2-S4, 18.4R3-S1; 19.1 versions prior to 19.1R1-S5, 19.1R2-S1, 19.1R3; 19.2 versions prior to 19.2R1-S5, 19.2R2; 19.3 versions prior to 19.3R2-S3, 19.3R3; 19.4 versions prior to 19.4R1-S2, 19.4R2. Versions of Junos OS prior to 17.4R1 are unaffected by this vulnerability.

Gravité et risque d'exploitation

CVE-2020-1653 obtient un score CVSS de 7.5/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 1.59 %, ce qui la place devant 75.3 % des CVE référencées.

Que faire ?

  • Vérifiez si Junos OS (versions <17.4R1, <18.1R3-S10, 19.2, 19.3, 18.2, <18.3R2-S4, 18.3R3-S2, <17.4R2-S11, 17.4R3-S2, 18.3, 19.1, <19.3R2-S3, 19.3R3, 18.1, 17.4, 18.4, <19.2R1-S5, 19.2R2, 19.4, <18.4R1-S7, 18.4R2-S4, 18.4R3-S1, 18.2X75, <18.2X75-D41, 18.2X75-D420.12, 18.2X75-D51, 18.2X75-D60, 18.2X75-D34, <19.1R1-S5, 19.1R2-S1, 19.1R3, <18.2R2-S7, 18.2R3-S5, <19.4R1-S2, 19.4R2) est présent sur votre parc.
  • Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
  • À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
  • Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.

Références