The version of Junos OS installed on the remote host is affected by a vulnerability as referenced in the JSA69713 advisory.    - A Missing Release of Memory after Effective Lifetime vulnerability in the kernel of Juniper Networks Junos     OS allows an unauthenticated network based attacker to cause a Denial of Service (DoS). On all Junos platforms, the Kernel Routing Table (KRT) queue can get stuck due to a memory leak triggered by interface     flaps or route churn leading to RIB and PFEs getting out of sync. The memory leak causes RTNEXTHOP/route     and next-hop memory pressure issue and the KRT queue will eventually get stuck with the error- 'ENOMEM --     Cannot allocate memory'. The out-of-sync state between RIB and FIB can be seen with the show route and     show route forwarding-table command. This issue will lead to failures for adding new routes. The KRT     queue status can be checked using the CLI command show krt queue: user@host > show krt state High-     priority add queue: 1 queued ADD nhtype Router index 0 (31212) error 'ENOMEM -- Cannot allocate memory'     kqp '0x8ad5e40' The following messages will be observed in /var/log/messages, which indicate high memory     for routes/nexthops: host rpd[16279]: RPD_RT_HWM_NOTICE: New RIB highwatermark for routes: 266 [2022-03-04     05:06:07] host rpd[16279]: RPD_KRT_Q_RETRIES: nexthop ADD: Cannot allocate memory host rpd[16279]:     RPD_KRT_Q_RETRIES: nexthop ADD: Cannot allocate memory host kernel: rts_veto_net_delayed_unref_limit:
Route/nexthop memory is severe pressure. User Application to perform recovery actions. O p 8 err 12,     rtsm_id 0:-1, msg type 10, veto simulation: 0. host kernel: rts_veto_net_delayed_unref_limit: Memory usage     of M_RTNEXTHOP type = (806321208) Max size possible for M_RTNEXTHOP type = (689432176) Current delayed     unref = (0), Max delayed unref on this platform = (120000) Current delayed weight unref = (0) Max delayed     weight unref on this platform = (400000) curproc = rpd. This issue affects: Juniper Networks Junos OS 21.2     versions prior to 21.2R3; 21.3 versions prior to 21.3R2-S1, 21.3R3; 21.4 versions prior to 21.4R1-S2,     21.4R2; This issue does not affect Juniper Networks Junos OS versions prior to 21.2R1. (CVE-2022-22209)  Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.);   # http://www.nessus.org/u?99086ea4 script_set_attribute(attribute:see_also, value:http://www.nessus.org/u?99086ea4);   # http://www.nessus.org/u?b616ed59 script_set_attribute(attribute:see_also, value:http://www.nessus.org/u?b616ed59);   # http://www.nessus.org/u?0d4fd08b script_set_attribute(attribute:see_also, value:http://www.nessus.org/u?0d4fd08b);   # http://www.nessus.org/u?553f364c script_set_attribute(attribute:see_also, value:http://www.nessus.org/u?553f364c

Detections

Analytics

Juniper Junos OS Vulnerability (JSA69713)

high Nessus Plugin ID 163769

Version 1.7

Version 1.6

Version 1.5

Version 1.7 Jun 18, 2024, 8:57 PM IAVM reference Plugin Feed: 202406182057
Version 1.6 Jul 20, 2023, 8:11 PM CVSS temporal metrics ("CVSSv2 temporal vector" set to "CVSS2#E:POC/RL:OF/RC:C". "CVSSv3 temporal vector" set to "CVSS:3.0/E:P/RL:O/RC:C") Exploit attributes ("Exploit available" set to "True". "Exploitability ease" changed from "No known exploits are available" to "Exploits are available") Plugin metadata Plugin Feed: 202307202011
Version 1.5 Dec 7, 2022, 8:11 PM CVSS metrics ("CVSSv2 score" changed from "5.0" to "7.8") CVSS metrics ("CVSSv2 vector" changed from "CVSS2#AV:N/AC:L/Au:N/C:N/I:N/A:P" to "CVSS2#AV:N/AC:L/Au:N/C:N/I:N/A:C") CVSSv2 severity (based on CVE-2022-22209, severity increased from "Medium" to "High") Plugin Feed: 202212072011