medium
6.1
CWE
367 770 362
Advisory Published
Updated

CVE-2023-22397: Junos OS Evolved: PTX10003: An attacker sending specific genuine packets will cause a memory leak in the PFE leading to a Denial of Service

First published: Thu Jan 12 2023(Updated: )

An Allocation of Resources Without Limits or Throttling weakness in the memory management of the Packet Forwarding Engine (PFE) on Juniper Networks Junos OS Evolved PTX10003 Series devices allows an adjacently located attacker who has established certain preconditions and knowledge of the environment to send certain specific genuine packets to begin a Time-of-check Time-of-use (TOCTOU) Race Condition attack which will cause a memory leak to begin. Once this condition begins, and as long as the attacker is able to sustain the offending traffic, a Distributed Denial of Service (DDoS) event occurs. As a DDoS event, the offending packets sent by the attacker will continue to flow from one device to another as long as they are received and processed by any devices, ultimately causing a cascading outage to any vulnerable devices. Devices not vulnerable to the memory leak will process and forward the offending packet(s) to neighboring devices. Due to internal anti-flood security controls and mechanisms reaching their maximum limit of response in the worst-case scenario, all affected Junos OS Evolved devices will reboot in as little as 1.5 days. Reboots to restore services cannot be avoided once the memory leak begins. The device will self-recover after crashing and rebooting. Operator intervention isn't required to restart the device. This issue affects: Juniper Networks Junos OS Evolved on PTX10003: All versions prior to 20.4R3-S4-EVO; 21.3 versions prior to 21.3R3-S1-EVO; 21.4 versions prior to 21.4R2-S2-EVO, 21.4R3-EVO; 22.1 versions prior to 22.1R1-S2-EVO, 22.1R2-EVO; 22.2 versions prior to 22.2R2-EVO. To check memory, customers may VTY to the PFE first then execute the following show statement: show jexpr jtm ingress-main-memory chip 255 | no-more Alternatively one may execute from the RE CLI: request pfe execute target fpc0 command "show jexpr jtm ingress-main-memory chip 255 | no-more" Iteration 1: Example output: Mem type: NH, alloc type: JTM 136776 bytes used (max 138216 bytes used) 911568 bytes available (909312 bytes from free pages) Iteration 2: Example output: Mem type: NH, alloc type: JTM 137288 bytes used (max 138216 bytes used) 911056 bytes available (909312 bytes from free pages) The same can be seen in the CLI below, assuming the scale does not change: show npu memory info Example output: FPC0:NPU16 mem-util-jnh-nh-size 2097152 FPC0:NPU16 mem-util-jnh-nh-allocated 135272 FPC0:NPU16 mem-util-jnh-nh-utilization 6

Credit: sirt@juniper.net

Affected SoftwareAffected VersionHow to fix
Juniper Junos Os Evolved<20.4
Juniper Junos Os Evolved=20.4
Juniper Junos Os Evolved=20.4-r1
Juniper Junos Os Evolved=20.4-r1-s1
Juniper Junos Os Evolved=20.4-r1-s2
Juniper Junos Os Evolved=20.4-r2
Juniper Junos Os Evolved=20.4-r2-s1
Juniper Junos Os Evolved=20.4-r2-s2
Juniper Junos Os Evolved=20.4-r2-s3
Juniper Junos Os Evolved=20.4-r3
Juniper Junos Os Evolved=20.4-r3-s1
Juniper Junos Os Evolved=20.4-r3-s2
Juniper Junos Os Evolved=20.4-r3-s3
Juniper Junos Os Evolved=21.3
Juniper Junos Os Evolved=21.3-r1
Juniper Junos Os Evolved=21.3-r1-s1
Juniper Junos Os Evolved=21.3-r2
Juniper Junos Os Evolved=21.3-r2-s1
Juniper Junos Os Evolved=21.3-r2-s2
Juniper Junos Os Evolved=21.3-r3
Juniper Junos Os Evolved=21.4
Juniper Junos Os Evolved=21.4-r1
Juniper Junos Os Evolved=21.4-r1-s1
Juniper Junos Os Evolved=21.4-r1-s2
Juniper Junos Os Evolved=21.4-r2
Juniper Junos Os Evolved=21.4-r2-s1
Juniper Junos Os Evolved=22.1-r1
Juniper Junos Os Evolved=22.1-r1-s1
Juniper Junos Os Evolved=22.2-r1
Juniper Junos Os Evolved=22.2-r1-s1
Juniper Ptx10003

Remedy

The following software releases have been updated to resolve these specific issues: Junos OS Evolved: 20.4R3-S4-EVO, 21.3R3-S1-EVO, 21.4R2-S2-EVO, 21.4R3-EVO, 22.1R1-S2-EVO, 22.1R2-EVO, 22.1R3-EVO, 22.2R1-S1-EVO, 22.2R2-EVO, 22.3R1-EVO, and all subsequent releases.

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is CVE-2023-22397?

    CVE-2023-22397 is an Allocation of Resources Without Limits or Throttling weakness in the memory management of Juniper Networks Junos OS Evolved PTX10003 Series devices.

  • Which devices are affected by CVE-2023-22397?

    Juniper Networks Junos OS Evolved PTX10003 Series devices are affected by CVE-2023-22397.

  • What is the severity of CVE-2023-22397?

    CVE-2023-22397 has a severity level of 6.1 (Medium).

  • How can I fix the vulnerability CVE-2023-22397?

    To fix CVE-2023-22397, update your Juniper Networks Junos OS Evolved PTX10003 Series devices to version 20.4 or higher.

  • Where can I find more information about CVE-2023-22397?

    You can find more information about CVE-2023-22397 at the Juniper Networks Knowledge Base: https://kb.juniper.net/JSA70193

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203