5.9
CVE-2023-22402
- EPSS 0.23%
- Published 13.01.2023 00:15:10
- Last modified 21.11.2024 07:44:44
- Source sirt@juniper.net
- Teams watchlist Login
- Open Login
A Use After Free vulnerability in the kernel of Juniper Networks Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). In a Non Stop Routing (NSR) scenario, an unexpected kernel restart might be observed if "bgp auto-discovery" is enabled and if there is a BGP neighbor flap of auto-discovery sessions for any reason. This is a race condition which is outside of an attackers direct control and it depends on system internal timing whether this issue occurs. This issue affects Juniper Networks Junos OS Evolved: 21.3 versions prior to 21.3R3-EVO; 21.4 versions prior to 21.4R2-EVO; 22.1 versions prior to 22.1R2-EVO; 22.2 versions prior to 22.2R1-S1-EVO, 22.2R2-EVO.
Data is provided by the National Vulnerability Database (NVD)
Juniper ≫ Junos Os Evolved Version21.3 Update-
Juniper ≫ Junos Os Evolved Version21.3 Updater1
Juniper ≫ Junos Os Evolved Version21.3 Updater1-s1
Juniper ≫ Junos Os Evolved Version21.3 Updater2
Juniper ≫ Junos Os Evolved Version21.3 Updater2-s1
Juniper ≫ Junos Os Evolved Version21.3 Updater2-s2
Juniper ≫ Junos Os Evolved Version21.4 Update-
Juniper ≫ Junos Os Evolved Version21.4 Updater1
Juniper ≫ Junos Os Evolved Version21.4 Updater1-s1
Juniper ≫ Junos Os Evolved Version21.4 Updater1-s2
Juniper ≫ Junos Os Evolved Version22.1 Updater1
Juniper ≫ Junos Os Evolved Version22.1 Updater1-s1
Juniper ≫ Junos Os Evolved Version22.1 Updater1-s2
Juniper ≫ Junos Os Evolved Version22.2 Updater1
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
Type | Source | Score | Percentile |
---|---|---|---|
EPSS | FIRST.org | 0.23% | 0.46 |
Source | Base Score | Exploit Score | Impact Score | Vector string |
---|---|---|---|---|
sirt@juniper.net | 5.9 | 2.2 | 3.6 |
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
|
CWE-416 Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.