CybersecurityTech News

Security updates: Attackers could attack Juniper software with malicious code

The network supplier Juniper has closed critical security gaps in Contrail Networking, among other things.

 

For security reasons, admins of networks with Juniper software should update their systems as soon as possible. Otherwise, attackers could gain access to computers and, in the worst case, completely compromise them.

Further information on the gaps and versions secured against attacks can be found in the warning messages linked below this article.

Several are considered to be particularly dangerous as “critical‘ classified vulnerabilities in Contrail Networking. This is used to create and manage virtual networks. Attackers could target several vulnerabilities and trigger memory errors in a way that is not described in detail. This usually leads to a crash. Often, however, code from attackers also gets onto systems. The developers state Contrail Networking 21.4.0 to have repaired. All previous versions are said to be vulnerable.

Other critical vulnerabilities affect Junos Space for managing network devices and Northstar controllers. Attackers could, among other things, gain higher user rights here after successful attacks.

Most of the remaining gaps are at threat level “high“ classified. They affect the Junos OS network operating system. Attackers could primarily trigger DoS conditions here.

List sorted by threat level in descending order:

  • Contrail Networking: Multiple vulnerabilities resolved in Contrail Networking 21.4
  • Junos Space: Security Director Policy Enforcer upgraded to CentOS 7.9
  • Northstar Controller: nginx component allows remote attacker to cause worker process crash or potentially, arbitrary code execution (CVE-2021-23017)
  • Junos Space: Multiple vulnerabilities resolved in 22.1R1 release
  • Junos OS: SRX and EX Series: Local privilege escalation flaw in “download” functionality (CVE-2022-22221)
  • Junos OS: OpenSSL security fixes
  • Junos OS: SRX Series: An FPC memory leak can occur in an APBR scenario (CVE-2022-22205)
  • Junos OS Evolved: A high rate of specific hostbound traffic will cause unexpected hostbound traffic delays or drops (CVE-2022-22212)
  • Junos OS: MX Series with MPC11: In a GNF / node slicing scenario gathering AF interface statistics can lead to a kernel crash (CVE-2022-22207)
  • Junos OS: RIB and PFEs can get out of sync due to a memory leak caused by interface flaps or route churn (CVE-2022-22209)
  • Junos OS and Junos OS Evolved: Multiple vulnerabilities in SQLite resolved
  • Junos OS: SRX series: The PFE will crash when specific traffic is scanned by Enhanced Web Filtering safe-search (CVE-2022-22206)
  • Junos OS: PTX Series: FPCs may restart unexpectedly upon receipt of specific MPLS packets with certain multi-unit interface configurations (CVE-2022-22202)
  • Junos OS and Junos OS Evolved: In an MPLS scenario upon receipt of a specific IPv6 packet an FPC will crash (CVE-2022-22214)
  • Junos OS: EX4600 Series and QFX5000 Series: Receipt of specific traffic will lead to an fxpc process crash followed by an FPC reboot (CVE-2022-22203)
  • Junos OS and Junos OS Evolved: /var/run/.env files are potentially not deleted during termination of a gRPC connection causing inode exhaustion (CVE-2022-22215)
  • Junos OS: QFX5000 Series and MX Series: An l2alm crash leading to an FPC crash can be observed in VxLAN scenario (CVE-2022-22210)
  • Junos OS: QFX10K Series: Denial of Service (DoS) upon receipt of crafted MLD packets on multi-homing ESI in VXLAN (CVE-2022-22217)
  • Junos OS and Junos OS Evolved: Denial of Service (DoS) vulnerability in RPD upon receipt of specific BGP update (CVE-2022-22213)
  • Junos OS: MX Series and SRX Series: When receiving a specific SIP packets stale call table entries are created which eventually leads to a DoS for all SIP traffic (CVE-2022-22204)
  • Junos OS: PTX Series and QFX10000 Series: ‘Etherleak’ memory disclosure in Ethernet padding data (CVE-2022-22216)

Related Articles

Leave a Reply

Your email address will not be published. Required fields are marked *

Back to top button