OpenControls Logo

STIG Viewer

STIGViewer Support

The Nokia perimeter router must be configured to drop IPv6 packets containing an extension header with the Endpoint Identification option.

Overview

Finding IDVersionRule IDIA ControlsSeverity
V-283846NOKI-RT-000280SV-283846r1203787_ruleCCI-002403medium
Description
The optional and extensible natures of the IPv6 extension headers require higher scrutiny since many implementations do not always drop packets with headers they cannot recognize, which could cause a denial of service on the target device. In addition, the type, length, value (TLV) formatting enables headers to be very large. This option type is associated with the Nimrod Routing system and has no defining RFC document.
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-283846r1203787_chk)

This requirement is not applicable for the DODIN Backbone. Review the router switch configuration and determine if filters are bound to the applicable interfaces to drop IPv6 packets containing an option type value of 0x8A (Endpoint Identification) regardless of whether it appears in a Hop-by-Hop or Destination Option header. Verify the IPv6 filter has the HopByHop option set to "True", as shown in the example below: - show filter ipv6 40 Entry : 10 (Inactive) Description : (Not Specified) Log Id : n/a Src. IP : ::/0 Src. Port : n/a Dest. IP : ::/0 Dest. Port : n/a Next Header : Undefined Dscp : Undefined ICMP Type : Undefined ICMP Code : Undefined Sampling : Off Int. Sampling : On Tcp-flag : (Not Specified) Fragment : Off HopByHop Opt : True Routing Type0 : Off Verify an "Ing IPv6 Flt" has been applied to the interface, as shown in the example below: - show router interface "TO-PE2" detail | match "Ingr IPv6 Flt" Egr IPv6 Flt : none Ingr IPv6 Flt : 40 If the router is not configured to drop IPv6 packets containing an extension header with the Endpoint Identification option, this is a finding.

Fix Text (F-88316r1203786_fix)

Configure the router to drop IPv6 packets containing an option type value of 0x8A (Endpoint Identification) regardless of whether it appears in a Hop-by-Hop or Destination Option header. Configure the IPv6 filter, as shown in the example below: Note: This will drop all Hop-by-Hop Option headers. - configure filter ipv6-filter 40 create - config>filter>ipv6-filter# default-action forward - config>filter>ipv6-filter# entry 10 create - config>filter>ipv6-filter>entry$ match hop-by-hop-opt 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 40