Multiple NTP vulnerabilities have been resolved in Juniper Networks Junos OS and Junos OS Evolved by updating third party software where vulnerabilities were found during external security research.
These issues affect:
Juniper Networks Junos OS:
NTP must be operating on the device to be affected by these issues, for example, the following minimal configuration is necessary:
[set system ntp]
Juniper SIRT is not aware of any malicious exploitation of these vulnerabilities.
These issues were discovered during a external security research.Important security issues resolved include:
The following software releases have been updated to resolve these specific issues:
Junos OS: 12.3R12-S15, 12.3X48-D95, 14.1X53-D53, 15.1R7-S6, 15.1X49-D190, 16.1R7-S6, 16.2R3, 17.1R2-S11, 17.1R3-S1, 17.2R1-S9, 17.2R2-S8, 17.2R3-S3, 17.3R2-S5, 17.3R3-S6, 17.4R2-S7, 17.4R3, 18.1R3-S8, 18.2R2-S7, 18.2R3-S1, 18.3R1-S5, 18.3R2-S2, 18.3R3, 18.4R1-S4, 18.4R2-S1, 18.4R3, 19.1R1-S3, 19.1R2, 19.2R1-S1, 19.2R2, 19.3R1 and all subsequent releases.
Junos OS Evolved: 20.1R1-EVO, and subsequent releases.
After upgrading to a resolved release, the mitigations listed in the following advisories also need to be applied:
Then, the CLI must be configured using the ntp restrict command:
set system ntp restrict
mask <mask_addr> noquery
commit
Note 1: With the above configuration all masked source addresses (source_address & mask_addr) which matches with (address & mask_addr) are restricted to query ntpq/ntpdc to ntp server.
Note 2: The restriction of subnets is only available from Junos OS 20.1R1, and subsequent releases, and Junos OS Evolved 20.2R1-EVO, and subsequent releases.
An Example Configuration which allows all the hosts having address 192.168.0.<0-255> being unable to send ntpq/ntpdc query to ntp server from Junos OS 20.1R1, and onward, and Junos OS Evolved 20.2R1-EVO, and onward:
set system ntp restrict 192.168.0.1 mask 255.255.255.0 noquery
Note 3: The noquery option is a hidden command in all releases prior to Junos OS 20.1R1. The command may not persist across reboots, so care must be taken to ensure that it is written to the ntp configuration file. Contact Juniper Networks Technical Assistance Center (JTAC) for guided assistance if necessary.
If any of the above NTP mitigations are not in place, there is still the possibility of exploitability.
This issue is being tracked as PR 1269141, 1446493 and 1446497 .
Software releases or updates are available for download at https://support.juniper.net/support/downloads/
Use firewall filters to block NTP mode 6 query packets.Set system ntp restrict to block local ntpq <-> ntpd query responses. i.e. disallow 127.0.0.1 and -6 ::1 if allowed in addition to remote hosts.
2021-04-14: Initial Publication. 2023-05-02: Added additional CVEs. Updated Severity to High. Updated CVSS Score to 8.8. Added PR 1269141 to tracking. Included additional workaround guidance to set system ntp restrict to block local ntpq <-> ntpd query responses thus blocking all query responses from any location. i.e. disallow 127.0.0.1 and -6 ::1 if allowed in addition to remote hosts.