CVE-2023-22409

An Unchecked Input for Loop Condition vulnerability in a NAT library of Juniper Networks Junos OS allows a local authenticated attacker with low privileges to cause a Denial of Service (DoS). When an inconsistent "deterministic NAT" configuration is present on an SRX, or MX with SPC3 and then a specific CLI command is issued the SPC will crash and restart. Repeated execution of this command will lead to a sustained DoS. Such a configuration is characterized by the total number of port blocks being greater than the total number of hosts. An example for such configuration is: [ services nat source pool TEST-POOL address x.x.x.0/32 to x.x.x.15/32 ] [ services nat source pool TEST-POOL port deterministic block-size 1008 ] [ services nat source pool TEST-POOL port deterministic host address y.y.y.0/24] [ services nat source pool TEST-POOL port deterministic include-boundary-addresses] where according to the following calculation: 65536-1024=64512 (number of usable ports per IP address, implicit) 64512/1008=64 (number of port blocks per Nat IP) x.x.x.0/32 to x.x.x.15/32 = 16 (NAT IP addresses available in NAT pool) total port blocks in NAT Pool = 64 blocks per IP * 16 IPs = 1024 Port blocks host address y.y.y.0/24 = 256 hosts (with include-boundary-addresses) If the port block size is configured to be 4032, then the total port blocks are (64512/4032) * 16 = 256 which is equivalent to the total host addresses of 256, and the issue will not be seen. This issue affects Juniper Networks Junos OS on SRX Series, and MX Series with SPC3: All versions prior to 19.4R3-S10; 20.1 version 20.1R1 and later versions; 20.2 versions prior to 20.2R3-S6; 20.3 versions prior to 20.3R3-S6; 20.4 versions prior to 20.4R3-S5; 21.1 versions prior to 21.1R3-S4; 21.2 versions prior to 21.2R3-S3; 21.3 versions prior to 21.3R3-S3; 21.4 versions prior to 21.4R3-S1; 22.1 versions prior to 22.1R2-S2, 22.1R3; 22.2 versions prior to 22.2R2.

• CWE-1284

• https://kb.juniper.net/JSA70205Vendor Advisory
• https://kb.juniper.net/JSA70205Vendor Advisory

Published

Jan 13, 2023

Last Modified

Jun 17, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2023-22403 An Allocation of Resources Without Limits or Throttling vul…7.5
• CVE-2023-22404An Out-of-bounds Write vulnerability in the Internet Key Exc…6.5
• CVE-2023-22405An Improper Preservation of Consistency Between Independent …6.5
• CVE-2023-22406A Missing Release of Memory after Effective Lifetime vulnera…6.5
• CVE-2023-22407An Incomplete Cleanup vulnerability in the Routing Protocol …6.5
• CVE-2023-22408An Improper Validation of Array Index vulnerability in the S…7.5
• CVE-2023-2241A vulnerability, which was classified as critical, was found…5.3
• CVE-2023-22410A Missing Release of Memory after Effective Lifetime vulnera…6.5
• CVE-2023-22411An Out-of-Bounds Write vulnerability in Flow Processing Daem…7.5
• CVE-2023-22412An Improper Locking vulnerability in the SIP ALG of Juniper …7.5
• CVE-2023-22413An Improper Check or Handling of Exceptional Conditions vuln…7.5
• CVE-2023-22414A Missing Release of Memory after Effective Lifetime vulnera…6.5