First published: Wed Jul 20 2022(Updated: )
An Improper Release of Memory Before Removing Last Reference vulnerability in the Session Initiation Protocol (SIP) Application Layer Gateway (ALG) of Juniper Networks Junos OS allows unauthenticated network-based attacker to cause a partial Denial of Service (DoS). On all MX and SRX platforms, if the SIP ALG is enabled, receipt of a specific SIP packet will create a stale SIP entry. Sustained receipt of such packets will cause the SIP call table to eventually fill up and cause a DoS for all SIP traffic. The SIP call usage can be monitored by "show security alg sip calls". To be affected the SIP ALG needs to be enabled, either implicitly / by default or by way of configuration. Please verify on SRX with: user@host> show security alg status | match sip SIP : Enabled Please verify on MX whether the following is configured: [ services ... rule <rule-name> (term <term-name>) from/match application/application-set <name> ] where either a. name = junos-sip or an application or application-set refers to SIP: b. [ applications application <name> application-protocol sip ] or c. [ applications application-set <name> application junos-sip ] This issue affects Juniper Networks Junos OS on SRX Series and MX Series: 20.4 versions prior to 20.4R3-S2; 21.1 versions prior to 21.1R3-S2; 21.2 versions prior to 21.2R2-S2; 21.2 versions prior to 21.2R3; 21.3 versions prior to 21.3R2; 21.4 versions prior to 21.4R2. This issue does not affect Juniper Networks Junos OS versions prior to 20.4R1. Juniper SIRT is not aware of any malicious exploitation of this vulnerability.
Credit: sirt@juniper.net
Affected Software | Affected Version | How to fix |
---|---|---|
Juniper JUNOS | =20.4 | |
Juniper JUNOS | =20.4-r1 | |
Juniper JUNOS | =20.4-r1-s1 | |
Juniper JUNOS | =20.4-r2 | |
Juniper JUNOS | =20.4-r2-s1 | |
Juniper JUNOS | =20.4-r2-s2 | |
Juniper JUNOS | =20.4-r3 | |
Juniper JUNOS | =20.4-r3-s1 | |
Juniper JUNOS | =21.1 | |
Juniper JUNOS | =21.1-r1 | |
Juniper JUNOS | =21.1-r1-s1 | |
Juniper JUNOS | =21.1-r2 | |
Juniper JUNOS | =21.1-r2-s1 | |
Juniper JUNOS | =21.1-r2-s2 | |
Juniper JUNOS | =21.1-r3 | |
Juniper JUNOS | =21.1-r3-s1 | |
Juniper JUNOS | =21.2 | |
Juniper JUNOS | =21.2-r1 | |
Juniper JUNOS | =21.2-r1-s1 | |
Juniper JUNOS | =21.2-r1-s2 | |
Juniper JUNOS | =21.2-r2 | |
Juniper JUNOS | =21.2-r2-s1 | |
Juniper JUNOS | =21.3-r1 | |
Juniper JUNOS | =21.3-r1-s1 | |
Juniper JUNOS | =21.3-r1-s2 | |
Juniper JUNOS | =21.4-r1 | |
Juniper JUNOS | =21.4-r1-s1 | |
Juniper JUNOS | =21.4-r1-s2 | |
Juniper Mx10 | ||
Juniper Mx10000 | ||
Juniper Mx10003 | ||
Juniper Mx10008 | ||
Juniper Mx10016 | ||
Juniper Mx104 | ||
Juniper Mx150 | ||
Juniper Mx2008 | ||
Juniper Mx2010 | ||
Juniper Mx2020 | ||
Juniper Mx204 | ||
Juniper Mx240 | ||
Juniper Mx40 | ||
Juniper Mx480 | ||
Juniper Mx5 | ||
Juniper Mx80 | ||
Juniper Mx960 | ||
Juniper Srx100 | ||
Juniper Srx110 | ||
Juniper Srx1400 | ||
Juniper Srx1500 | ||
Juniper Srx210 | ||
Juniper Srx220 | ||
Juniper Srx240 | ||
Juniper Srx240h2 | ||
Juniper Srx300 | ||
Juniper Srx320 | ||
Juniper Srx340 | ||
Juniper Srx3400 | ||
Juniper Srx345 | ||
Juniper Srx3600 | ||
Juniper Srx380 | ||
Juniper Srx4000 | ||
Juniper Srx4100 | ||
Juniper Srx4200 | ||
Juniper Srx4600 | ||
Juniper Srx5000 | ||
Juniper Srx5400 | ||
Juniper Srx550 | ||
Juniper Srx550 Hm | ||
Juniper Srx550m | ||
Juniper Srx5600 | ||
Juniper Srx5800 | ||
Juniper Srx650 |
The following software releases have been updated to resolve this specific issue: 20.4R3-S2, 21.1R3-S2, 21.2R2-S2, 21.2R3, 21.3R2, 21.4R2, 22.1R1, and all subsequent releases.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.