OpenControls Logo

STIG Viewer

STIGViewer Support

The Nokia perimeter router must be configured drop IPv6 packets with a Routing Header type of 0, 1, or 3-255.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-283840NOKI-RT-000220SV-283840r1203769_ruleCCI-002403medium
Description
The Routing Header can be used maliciously to send a packet through a path where less robust security is in place, rather than through the presumably preferred path of routing protocols. Use of the Routing Extension Header has few legitimate uses other than as implemented by Mobile IPv6. The Type 0 Routing Header (RFC 5095) is dangerous because it allows attackers to spoof source addresses and obtain traffic in response, rather than the real owner of the address. Also, a packet with an allowed destination address could be sent through a Firewall using the Routing Header functionality, only to bounce to a different node once inside. The Type 1 Routing Header is defined by a specification called "Nimrod Routing", a discontinued project funded by the Defense Advanced Research Projects Agency (DARPA). Assuming that most implementations will not recognize the Type 1 Routing Header, it must be dropped. The Type 3-255 Routing Header values in the routing type field are currently undefined and should be dropped inbound and outbound.
STIGDate
Nokia Service Router OS 25.x Router Security Technical Implementation Guide2026-06-15

Related Frameworks

1 mapping across 3 frameworks
SCF0 mappings

No source states a mapping between these directly.

Also reachable in 3 hops (2) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

NET-03Boundary Protection
0.50
NET-04.1Deny Traffic by Default & Allow Traffic by Exception
0.50
NIST 800-530 mappings

No source states a mapping between these directly.

Also reachable in 2 hops (8) derived by us, not asserted by any source

Each of these is a route we composed by chaining published mappings. No publisher states a relationship between the two endpoints.

CM-6Configuration Settings
1.00
SC-24Fail in Known State
1.00
SC-47Alternate Communications Paths
1.00
SC-5Denial-of-service Protection
1.00
SC-7Boundary Protection
1.00
SC-7(11)Restrict Incoming Communications Traffic
1.00
SC-7(29)Separate Subnets to Isolate Functions
1.00
SC-7(5)Deny by Default — Allow by Exception
1.00
CCI1 mapping
CCI-002403
1.00

Details

Check Text (C-283840r1203769_chk)

This requirement is not applicable for the DODIN Backbone. Review the router configuration to determine if it is configured to drop IPv6 packets containing a Routing Header of type 0, 1, or 3-255. Use the command below and determine if any "Ingr IPv6 Flt" is applied: - show router interface "TO-PE2" detail | match "Ingr IPv6 Flt" Egr IPv6 Flt : none Ingr IPv6 Flt : 20 If the router is not configured to drop IPv6 packets containing a Routing Header of type 0, 1, or 3-255, this is a finding.

Fix Text (F-88310r1203768_fix)

Configure the router to drop IPv6 packets with Routing Header of type 0, 1, or 3-255. Configure an IPv6 filter, as shown in the example below: - configure filter ipv6-filter 20 create - config>filter>ipv6-filter# entry 20 create - config>filter>ipv6-filter>entry$ match routing-type0 true - config>filter>ipv6-filter>entry$ action drop - config>filter>ipv6-filter>entry$ exit all Apply the IPv6 filter to the interface: - configure router interface "TO-PE2" ingress filter ipv6 20