2019-07 Security Bulletin: Junos OS: Multiple Vulnerabilities in OpenSSH

Multiple vulnerabilities have been resolved in Junos OS by updating third party software included with Junos OS or by fixing vulnerabilities found during internal testing. For further information refer to JSA10940 [juniper.net].

The PFE process might crash in scenario with large log messages on EX switch

On EX Series switches except EX4300/EX4600/EX9200, when RTG (Redundant Trunk Group) switchovers are done, then the /var/log/shadow.log or /var/log/shadow_debug.log is rotated. And it might cause PFE process to crash.

802.1x authentication issue might be seen on Legacy EX platforms in mac-radius multi-supplicant mode

On Legacy EX platforms (EX2200/EX3200/EX3300/EX4200/EX45/EX62/EX82) with RE protect filter configured (firewall filter applied on loopback interface), when an interface is using 802.1x mac-radius multi-supplicant mode and there are more than one devices daisy-chained on the interface, MAC learning messages for unknown source might be dropped, which will cause 802.1x legitimate users fail to be authenticated.

The ERPS ring may fail and traffic may lose on EX

On the EX-series switch with ERPS configured scenario, if one of the ERPS (Ethernet Ring Protection Switching) interfaces is deleted by unplugging transceiver, eswd (ethernet switching process) crash and ERPS PDUs won't be sent anymore. This issue may cause the ERPS ring failure and traffic loss.

The dot1x authentication might fail to be authenticated on some EX platforms

On EX2200/EX3200/EX3300/EX4200/EX4500/EX4550/EX6200/EX8200/EX8208/EX8016 Series platforms, the dot1x authentication might fail to be authenticated because the EX device doesn't strip the VLAN tag/priority for the tagged EAP responses packets.

Junos OS: Insufficient validation of environment variables in telnet client may lead to stack-based buffer overflow (CVE-2019-0053)

In Junos OS, insufficient validation of environment variables in telnet client may lead to stack-based buffer overflow (CVE-2019-0053); Refer to https://kb.juniper.net/JSA10947 [juniper.net] for more information.

MAC address might be learned as persistent on the trunk interface

MAC address might be learned as persistent on trunk interface when configured with both trunk interface and "ethernet-switching-options secure-access-port interface all persistent-learning" on EX2200/EX3200/EX3300/EX4200/EX4500/EX4550/EX6200/EX8200 platforms. The reason for this issue is the validation for the trunk port always fail during interface "all" configuration parsing.