Page 35 of 490 results (0.006 seconds)

CVSS: 5.5EPSS: 0%CPEs: 147EXPL: 0

When a MX Series is configured as a Broadband Network Gateway (BNG) based on Layer 2 Tunneling Protocol (L2TP), executing certain CLI command may cause the system to run out of disk space, excessive disk usage may cause other complications. An administrator can use the following CLI command to monitor the available disk space: user@device> show system storage Filesystem Size Used Avail Capacity Mounted on /dev/gpt/junos 19G 18G 147M 99% /.mount <<<<< running out of space tmpfs 21G 16K 21G 0% /.mount/tmp tmpfs 5.3G 1.7M 5.3G 0% /.mount/mfs This issue affects Juniper Networks Junos OS on MX Series: 17.3R1 and later versions prior to 17.4R3-S5, 18.1 versions prior to 18.1R3-S13, 18.2 versions prior to 18.2R3-S7; 18.3 versions prior to 18.3R3-S4; 18.4 versions prior to 18.4R3-S7; 19.1 versions prior to 19.1R3-S4; 19.2 versions prior to 19.2R1-S6, 19.2R3-S2; 19.3 versions prior to 19.3R3-S2; 19.4 versions prior to 19.4R2-S4, 19.4R3-S2; 20.1 versions prior to 20.1R3; 20.2 versions prior to 20.2R2-S3, 20.2R3; 20.3 versions prior to 20.3R2; 20.4 versions prior to 20.4R1-S1, 20.4R2; This issue does not affect Juniper Networks Junos OS versions prior to 17.3R1. Cuando una Serie MX se configura como Broadband Network Gateway (BNG) basada en el protocolo Layer 2 Tunneling Protocol (L2TP), la ejecución de determinados comandos de la CLI puede hacer que el sistema se quede sin espacio en el disco, el uso excesivo del disco puede causar otras complicaciones.&#xa0;Un administrador puede usar el siguiente comando CLI para monitorear el espacio disponible en disco: user@device&gt; show system storage Filesystem Size Used Avail Capacity Mounted on /dev/gpt/junos 19G 18G 147M 99% /.mount &lt;&lt;&lt;&lt;&lt; running out of space tmpfs 21G 16K 21G 0% /.mount/tmp tmpfs 5.3G 1.7M 5.3G 0% /.mount/mfs. Este problema afecta a Juniper Networks Junos OS en la serie MX: 17.3R1 y posteriores, versiones anteriores a 17.4R3-S5, versiones 18.1 anteriores a 18.1R3-S13, versiones 18.2 anteriores a 18.2R3-S7;&#xa0;versiones 18.3 anteriores a 18.3R3-S4;&#xa0;versiones 18.4 anteriores a 18.4R3-S7;&#xa0;versiones 19.1 anteriores a 19.1R3-S4;&#xa0;19. • https://kb.juniper.net/JSA11133 • CWE-400: Uncontrolled Resource Consumption •

CVSS: 6.5EPSS: 0%CPEs: 226EXPL: 0

On Juniper Networks EX4300-MP Series, EX4600 Series, EX4650 Series, QFX5K Series deployed as a Virtual Chassis with a specific Layer 2 circuit configuration, Packet Forwarding Engine manager (FXPC) process may crash and restart upon receipt of specific layer 2 frames. Continued receipt and processing of this packet will create a sustained Denial of Service (DoS) condition. This issue affects: Juniper Networks Junos OS on EX4300-MP Series, EX4600 Series, EX4650 Series, QFX5K Series 15.1 versions prior to 15.1R7-S9; 17.3 versions prior to 17.3R3-S11; 17.4 versions prior to 17.4R2-S13, 17.4R3-S4, 17.4R3-S5; 18.2 versions prior to 18.2R3-S8; 18.3 versions prior to 18.3R3-S4; 18.4 versions prior to 18.4R2-S7, 18.4R3-S6; 19.1 versions prior to 19.1R3-S4; 19.2 versions prior to 19.2R1-S6, 19.2R3-S1; 19.3 versions prior to 19.3R3-S1; 19.4 versions prior to 19.4R2-S4, 19.4R3-S1; 20.1 versions prior to 20.1R2; 20.2 versions prior to 20.2R2, 20.2R3; 20.3 versions prior to 20.3R1-S2, 20.3R2; En Juniper Networks Serie EX4300-MP, Serie EX4600, Serie EX4650, Serie QFX5K implementadas como un Virtual Chassis con una configuración de circuito de capa 2 específica, el proceso del Packet Forwarding Engine manager (FXPC) puede bloquearse y reiniciarse al recibir tramas de capa 2 específicas.&#xa0;La recepción y el procesamiento continuo de este paquete crearán una condición sostenida de Denegación de Servicio (DoS).&#xa0;Este problema afecta a: Juniper Networks Junos OS en las versiones Serie EX4300-MP, Serie EX4600, Serie EX4650, Serie QFX5K versiones 15.1 anteriores a 15.1R7-S9;&#xa0;versiones 17.3 anteriores a 17.3R3-S11;&#xa0;versiones 17.4 anteriores a 17.4R2-S13, 17.4R3-S4, 17.4R3-S5;&#xa0;versiones 18.2 anteriores a 18.2R3-S8;&#xa0;versiones 18.3 anteriores a 18.3R3-S4;&#xa0;versiones 18.4 anteriores a 18.4R2-S7, 18.4R3-S6;&#xa0;versiones 19.1 anteriores a 19.1R3-S4;&#xa0;versiones 19.2 anteriores a 19.2R1-S6, 19.2R3-S1;&#xa0;versiones 19.3 anteriores a 19.3R3-S1;&#xa0;versiones 19.4 anteriores a 19.4R2-S4, 19.4R3-S1;&#xa0;versiones 20.1 anteriores a 20.1R2;&#xa0;versiones 20.2 anteriores a 20.2R2, 20.2R3;&#xa0;versiones 20.3 anteriores a 20.3R1-S2, 20.3R2; • https://kb.juniper.net/JSA11132 •

CVSS: 5.8EPSS: 0%CPEs: 144EXPL: 0

Due to an improper Initialization vulnerability on Juniper Networks Junos OS QFX5100-96S devices with QFX 5e Series image installed, ddos-protection configuration changes will not take effect beyond the default DDoS (Distributed Denial of Service) settings when configured from the CLI. The DDoS protection (jddosd) daemon allows the device to continue to function while protecting the packet forwarding engine (PFE) during the DDoS attack. When this issue occurs, the default DDoS settings within the PFE apply, as CPU bound packets will be throttled and dropped in the PFE when the limits are exceeded. To check if the device has this issue, the administrator can execute the following command to monitor the status of DDoS protection: user@device> show ddos-protection protocols error: the ddos-protection subsystem is not running This issue affects only QFX5100-96S devices. No other products or platforms are affected by this issue. • https://kb.juniper.net/JSA11129 • CWE-665: Improper Initialization •

CVSS: 7.5EPSS: 0%CPEs: 25EXPL: 0

A vulnerability in Juniper Networks Junos OS ACX500 Series, ACX4000 Series, may allow an attacker to cause a Denial of Service (DoS) by sending a high rate of specific packets to the device, resulting in a Forwarding Engine Board (FFEB) crash. Continued receipt of these packets will sustain the Denial of Service (DoS) condition. This issue affects Juniper Networks Junos OS on ACX500 Series, ACX4000 Series: 17.4 versions prior to 17.4R3-S2. Una vulnerabilidad en Juniper Networks Junos OS en las Series ACX500, ACX4000, puede permitir a un atacante causar una Denegación de Servicio (DoS) mediante el envío de una alta tasa de paquetes específicos hacia el dispositivo, resultando en un bloqueo de Forwarding Engine Board (FFEB).&#xa0;La recepción continua de estos paquetes mantendrá la condición de Denegación de Servicio (DoS). • https://kb.juniper.net/JSA11128 • CWE-400: Uncontrolled Resource Consumption CWE-794: Incomplete Filtering of Multiple Instances of Special Elements •

CVSS: 7.5EPSS: 0%CPEs: 208EXPL: 0

On Juniper Networks SRX Series devices with link aggregation (lag) configured, executing any operation that fetches Aggregated Ethernet (AE) interface statistics, including but not limited to SNMP GET requests, causes a slow kernel memory leak. If all the available memory is consumed, the traffic will be impacted and a reboot might be required. The following log can be seen if this issue happens. /kernel: rt_pfe_veto: Memory over consumed. Op 1 err 12, rtsm_id 0:-1, msg type 72 /kernel: rt_pfe_veto: free kmem_map memory = (20770816) curproc = kmd An administrator can use the following CLI command to monitor the status of memory consumption (ifstat bucket): user@device > show system virtual-memory no-forwarding | match ifstat Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) ifstat 2588977 162708K - 19633958 <<<< user@device > show system virtual-memory no-forwarding | match ifstat Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) ifstat 3021629 189749K - 22914415 <<<< This issue affects Juniper Networks Junos OS on SRX Series: 17.1 versions 17.1R3 and above prior to 17.3R3-S11; 17.4 versions prior to 17.4R3-S5; 18.2 versions prior to 18.2R3-S7, 18.2R3-S8; 18.3 versions prior to 18.3R3-S4; 18.4 versions prior to 18.4R2-S7, 18.4R3-S6; 19.1 versions prior to 19.1R3-S4; 19.2 versions prior to 19.2R1-S6; 19.3 versions prior to 19.3R3-S1; 19.4 versions prior to 19.4R3-S1; 20.1 versions prior to 20.1R2, 20.1R3; 20.2 versions prior to 20.2R2-S2, 20.2R3; 20.3 versions prior to 20.3R1-S2, 20.3R2. • https://kb.juniper.net/JSA11125 • CWE-400: Uncontrolled Resource Consumption CWE-401: Missing Release of Memory after Effective Lifetime •