Detections
Analytics

JUEX-RT-000290 - The Juniper router must be configured to use encryption for routing protocol authentication.

Warning! Audit Deprecated

This audit has been deprecated and will be removed in a future update.

View Next Audit Version

Information

A rogue router could send a fictitious routing update to convince a site's perimeter router to send traffic to an incorrect or even a rogue destination. This diverted traffic could be analyzed to learn confidential information about the site's network or used to disrupt the network's ability to communicate with other networks. This is known as a 'traffic attraction attack' and is prevented by configuring neighbor router authentication for routing updates. However, using clear-text authentication provides little benefit since an attacker can intercept traffic and view the authentication key. This would allow the attacker to use the authentication key in an attack.

This requirement applies to all IPv4 and IPv6 protocols that are used to exchange routing or packet forwarding information; this includes all Interior Gateway Protocols (such as OSPF, EIGRP, and IS-IS) and Exterior Gateway Protocols (such as BGP), MPLS-related protocols (such as LDP), and multicast-related protocols.

NOTE: Nessus has not performed this check. Please review the benchmark to ensure target compliance.

Solution

Configure routing protocol authentication to encrypt the authentication key.

set protocols ospf area <area number> interface <interface name>.<logical unit> authentication md5 <key ID> key '<PSK>'
-or-
set protocols ospf area <area number> interface <interface name>.<logical unit> ipsec-sa <SA name>

set protocols ospf3 area <area number> interface <interface name>.<logical unit> ipsec-sa <SA name>

set security ipsec security-association <SA name> mode transport
set security ipsec security-association <SA name> manual direction bidirectional protocol (ah | esp | bundle)
set security ipsec security-association <SA name> manual direction bidirectional spi <manually configured SPI (256..16639)>
set security ipsec security-association <SA name> manual direction bidirectional encryption algorithm (hmac-sha1-96 | hmac-sha-256-128)
set security ipsec security-association <SA name> manual direction bidirectional authentication key hexadecimal '<appropriate PSK>'
Note: Encryption keys can also be entered as ASCII with the keyword 'ascii-text' replacing 'hexadecimal'. Regardless of key type, the PSK is hashed in the configuration.

See Also

https://dl.dod.cyber.mil/wp-content/uploads/stigs/zip/U_Juniper_EX_Switches_Y24M01_STIG.zip

Item Details

References: CAT|II, CCI|CCI-000803, Rule-ID|SV-254001r844036_rule, STIG-ID|JUEX-RT-000290, Vuln-ID|V-254001

Plugin: Juniper

Control ID: 74f153af316acb7ac4b1e75e5724d4f06259c81e5f5585a1fb914501fcbfd9f4