ID CVE-2022-22164
Summary An Improper Initialization vulnerability in Juniper Networks Junos OS Evolved may cause a commit operation for disabling the telnet service to not take effect as expected, resulting in the telnet service staying enabled. When it is not intended to be operating on the device, an administrator can issue the following command to verify whether telnet is operating in the background: user@device > show system connections | grep :23 tcp 0 0 0.0.0.0:23 0.0.0.0:* LISTEN 20879/xinetd This issue affects: Juniper Networks Junos OS Evolved All versions prior to 20.4R2-S2-EVO; 21.1 version 21.1R1-EVO and later versions; 21.2 versions prior to 21.2R2-EVO.
References
Vulnerable Configurations
  • cpe:2.3:o:juniper:junos_os_evolved:20.4:-:*:*:*:*:*:*
    cpe:2.3:o:juniper:junos_os_evolved:20.4:-:*:*:*:*:*:*
  • cpe:2.3:o:juniper:junos_os_evolved:20.4:r1:*:*:*:*:*:*
    cpe:2.3:o:juniper:junos_os_evolved:20.4:r1:*:*:*:*:*:*
  • cpe:2.3:o:juniper:junos_os_evolved:20.4:r1-s1:*:*:*:*:*:*
    cpe:2.3:o:juniper:junos_os_evolved:20.4:r1-s1:*:*:*:*:*:*
  • cpe:2.3:o:juniper:junos_os_evolved:20.4:r1-s2:*:*:*:*:*:*
    cpe:2.3:o:juniper:junos_os_evolved:20.4:r1-s2:*:*:*:*:*:*
  • cpe:2.3:o:juniper:junos_os_evolved:20.4:r2:*:*:*:*:*:*
    cpe:2.3:o:juniper:junos_os_evolved:20.4:r2:*:*:*:*:*:*
  • cpe:2.3:o:juniper:junos_os_evolved:20.4:r2-s1:*:*:*:*:*:*
    cpe:2.3:o:juniper:junos_os_evolved:20.4:r2-s1:*:*:*:*:*:*
  • cpe:2.3:o:juniper:junos_os_evolved:20.4:r2-s2:*:*:*:*:*:*
    cpe:2.3:o:juniper:junos_os_evolved:20.4:r2-s2:*:*:*:*:*:*
  • cpe:2.3:o:juniper:junos_os_evolved:20.4:r2-s3:*:*:*:*:*:*
    cpe:2.3:o:juniper:junos_os_evolved:20.4:r2-s3:*:*:*:*:*:*
  • cpe:2.3:o:juniper:junos_os_evolved:20.4:r3-s1:*:*:*:*:*:*
    cpe:2.3:o:juniper:junos_os_evolved:20.4:r3-s1:*:*:*:*:*:*
  • cpe:2.3:o:juniper:junos_os_evolved:21.1:-:*:*:*:*:*:*
    cpe:2.3:o:juniper:junos_os_evolved:21.1:-:*:*:*:*:*:*
  • cpe:2.3:o:juniper:junos_os_evolved:21.2:-:*:*:*:*:*:*
    cpe:2.3:o:juniper:junos_os_evolved:21.2:-:*:*:*:*:*:*
CVSS
Base: 5.0 (as of 26-01-2022 - 02:21)
Impact:
Exploitability:
CWE CWE-665
CAPEC
  • Leveraging Race Conditions
    The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with his version and cause the system to read the malicious file.
  • Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions
    This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
NONE PARTIAL NONE
cvss-vector via4 AV:N/AC:L/Au:N/C:N/I:P/A:N
Last major update 26-01-2022 - 02:21
Published 19-01-2022 - 01:15
Last modified 26-01-2022 - 02:21
Back to Top