ID
VAR-202207-0863
CVE
CVE-2022-22209
TITLE
Juniper Networks Junos OS Vulnerability regarding lack of memory release after expiration in
Trust: 0.8
DESCRIPTION
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
Trust: 1.8
AFFECTED PRODUCTS
| vendor: | juniper | model: | junos | scope: | eq | version: | 21.4 | Trust: 1.0 |
| vendor: | juniper | model: | junos | scope: | eq | version: | 21.3 | Trust: 1.0 |
| vendor: | juniper | model: | junos | scope: | eq | version: | 21.2 | Trust: 1.0 |
| vendor: | ジュニパーネットワークス | model: | junos os | scope: | eq | version: | 21.4 | Trust: 0.8 |
| vendor: | ジュニパーネットワークス | model: | junos os | scope: | - | version: | - | Trust: 0.8 |
| vendor: | ジュニパーネットワークス | model: | junos os | scope: | eq | version: | - | Trust: 0.8 |
| vendor: | ジュニパーネットワークス | model: | junos os | scope: | eq | version: | 21.2 | Trust: 0.8 |
| vendor: | ジュニパーネットワークス | model: | junos os | scope: | eq | version: | 21.3 | Trust: 0.8 |
CVSS
SEVERITY | CVSSV2 | CVSSV3 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
PROBLEMTYPE DATA
| problemtype: | CWE-401 | Trust: 1.1 |
| problemtype: | Lack of memory release after expiration (CWE-401) [ others ] | Trust: 0.8 |
THREAT TYPE
remote
Trust: 0.6
TYPE
other
Trust: 0.6
EXTERNAL IDS
| db: | NVD | id: | CVE-2022-22209 | Trust: 3.4 |
| db: | JUNIPER | id: | JSA69713 | Trust: 2.6 |
| db: | JVNDB | id: | JVNDB-2022-013707 | Trust: 0.8 |
| db: | CNNVD | id: | CNNVD-202207-1227 | Trust: 0.6 |
| db: | VULHUB | id: | VHN-409738 | Trust: 0.1 |
| db: | VULMON | id: | CVE-2022-22209 | Trust: 0.1 |
REFERENCES
| url: | https://kb.juniper.net/jsa69713 | Trust: 2.6 |
| url: | https://nvd.nist.gov/vuln/detail/cve-2022-22209 | Trust: 0.8 |
| url: | https://vigilance.fr/vulnerability/junos-os-memory-leak-via-kernel-routing-table-38796 | Trust: 0.6 |
| url: | https://cxsecurity.com/cveshow/cve-2022-22209/ | Trust: 0.6 |
| url: | https://cwe.mitre.org/data/definitions/401.html | Trust: 0.1 |
| url: | https://nvd.nist.gov | Trust: 0.1 |
SOURCES
| db: | VULHUB | id: | VHN-409738 |
| db: | VULMON | id: | CVE-2022-22209 |
| db: | JVNDB | id: | JVNDB-2022-013707 |
| db: | CNNVD | id: | CNNVD-202207-1227 |
| db: | NVD | id: | CVE-2022-22209 |
LAST UPDATE DATE
2024-08-14T14:37:26.896000+00:00
SOURCES UPDATE DATE
| db: | VULHUB | id: | VHN-409738 | date: | 2022-07-29T00:00:00 |
| db: | VULMON | id: | CVE-2022-22209 | date: | 2022-07-20T00:00:00 |
| db: | JVNDB | id: | JVNDB-2022-013707 | date: | 2023-09-11T08:17:00 |
| db: | CNNVD | id: | CNNVD-202207-1227 | date: | 2022-08-10T00:00:00 |
| db: | NVD | id: | CVE-2022-22209 | date: | 2022-07-29T22:06:22.440 |
SOURCES RELEASE DATE
| db: | VULHUB | id: | VHN-409738 | date: | 2022-07-20T00:00:00 |
| db: | VULMON | id: | CVE-2022-22209 | date: | 2022-07-20T00:00:00 |
| db: | JVNDB | id: | JVNDB-2022-013707 | date: | 2023-09-11T00:00:00 |
| db: | CNNVD | id: | CNNVD-202207-1227 | date: | 2022-07-13T00:00:00 |
| db: | NVD | id: | CVE-2022-22209 | date: | 2022-07-20T15:15:08.643 |