Product Affected

This issue affects Junos OS 20.4, 21.1, 21.2, 21.3, 21.4, 22.1, 22.2, 22.3. Affected platforms: MX Series, SRX Series.
Medium
5.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N)

Problem

An Improper Check for Unusual or Exceptional Conditions vulnerability in the SIP ALG of Juniper Networks Junos OS on SRX Series and MX Series allows an unauthenticated network-based attacker to cause an integrity impact in connected networks.


If the SIP ALG is configured and a device receives a specifically malformed SIP packet, the device prevents this packet from being forwarded, but any subsequently received retransmissions of the same packet are forwarded as if they were valid.


This issue affects Juniper Networks Junos OS on SRX Series and MX Series:

  • 20.4 versions prior to 20.4R3-S5;
  • 21.1 versions prior to 21.1R3-S4;
  • 21.2 versions prior to 21.2R3-S4;
  • 21.3 versions prior to 21.3R3-S3;
  • 21.4 versions prior to 21.4R3-S2;
  • 22.1 versions prior to 22.1R2-S2, 22.1R3;
  • 22.2 versions prior to 22.2R2-S1, 22.2R3;
  • 22.3 versions prior to 22.3R1-S2, 22.3R2.

This issue doesn't not affected releases prior to 20.4R1.


To be affected the SIP ALG needs to be enabled, either implicitly / by default or by way of configuration. Please verify on SRX, and MX with SPC3 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 ]


Juniper SIRT is not aware of any malicious exploitation of this vulnerability.


This issue was found during internal product security testing or research.


This issue has been assigned CVE-2023-44198.

Solution

The following software releases have been updated to resolve this specific issue: 20.4R3-S5, 21.1R3-S4, 21.2R3-S4, 21.3R3-S3, 21.4R3-S2, 22.1R2-S2, 22.1R3, 22.2R2-S1, 22.2R3, 22.3R1-S2, 22.3R2, 22.4R1, and all subsequent releases.


This issue is being tracked as PR 1693379 which is visible on the Customer Support website.


Note: Juniper SIRT's policy [juniper.net] is not to evaluate releases which are beyond End of Engineering (EOE) or End of Life (EOL).

Workaround

There are no known workarounds for this issue.

Severity Assessment

Information for how Juniper Networks uses CVSS can be found at KB 16446 [juniper.net] "Common Vulnerability Scoring System (CVSS) and Juniper's Security Advisories."

Modification History

2023-10-11: Initial Publication

Related Information