Title

The Juniper router must be configured to authenticate all routing protocol messages using NIST-validated FIPS 198-1 message authentication code algorithm. (Cat II impact)

Discussion

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. Since MD5 is vulnerable to "birthday" attacks and may be compromised, routing protocol authentication must use FIPS 198-1 validated algorithms and modules to encrypt the authentication key. 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.

Check Content

Review the router configuration to verify it is using a NIST-validated FIPS 198-1 message authentication code algorithm to authenticate routing protocol messages. OSPF, both v2 and v3, and BGP support using a transport mode IP Security (IPsec) Security Association (SA) for authentication in addition to the protocol-standard authentication methods. Verify the IPsec SA is using an appropriate hashed message authentication code (HMAC). [edit security ipsec] security-association <SA name> { mode transport; manual { direction bidirectional { protocol (ah | esp | bundle); spi (256..16639); <<< The SPI is an integer value that must match the peer authentication { algorithm (hmac-sha1-96 | hmac-sha-256-128); key hexadecimal "hashed value"; ## SECRET-DATA } } } } Verify EGP (e.g., BGP) and IGP (e.g., OSPF) are configured to use an IPsec SA for authentication. [edit protocols] bgp { group <BGP group name> { <...snipped configuration...> neighbor <IPv4 neighbor address> { <...snipped protocol family configuration...> ipsec-sa <SA name>; } neighbor <IPv6 neighbor address> { <...snipped protocol family configuration...> ipsec-sa <SA name>; } } } ospf { area <OSPFv2 area number> { interface <OSPFv2 interface name>.<logical unit number> { <...snipped configuration...> ipsec-sa <SA name>; } } ospf3 { area <OSPFv3 area number> { interface <OSPFv3 interface name>.<logical unit number> { <...snipped configuration...> ipsec-sa <SA name>; } } If a NIST-validated FIPS 198-1 message authentication code algorithm is not being used to authenticate routing protocol messages, this is a finding.

Fix Text

Configure routing protocol authentication to use a NIST-validated FIPS 198-1 message authentication code algorithm. Configure the IPsec SA: 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 authentication 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. Configure EGP / IGP to use IPsec SA for authentication: set protocols bgp group <BGP group name> neighbor <IPv4 neighbor address> ipsec-sa <SA name> set protocols bgp group <BGP group name> neighbor <IPv6 neighbor address> ipsec-sa <SA name> set protocols ospf area <OSPFv2 area number> interface <interface name>.<logical unit> ipsec-sa <SA name> set protocols ospf3 area <OSPFv3 area number> interface <interface name>.<logical unit> ipsec-sa <SA name>

Additional Identifiers

Rule ID: SV-254002r844039_rule

Vulnerability ID: V-254002

Group Title: SRG-NET-000168-RTR-000078

Expert Comments

CCIs tied to check.

Controls tied to check. These are derived from the CCIs shown above.