Mobile IPv6 Binding Cache Used Field Replay Attack Prevention

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In Mobile IPv6 environments, mobile nodes are vulnerable to replay attacks during handoff, as attackers can exploit valid nonces to initiate unauthorized binding updates using previous Care of Addresses and Home Addresses.

Innovation Solution

The method involves setting a 'Used' field in binding entries to a predetermined value when the binding lifetime is 0 and the nonce is valid, and sending a reauthentication command message upon detecting a matching binding update from an attacker or mobile node, ensuring reauthentication and preventing replay attacks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Duration of action of moving object

If the binding lifetime is set to 0 and the nonce is valid, then the mobile node can perform seamless handoff and maintain communication, but the system becomes vulnerable to replay attacks

Engineering Contradiction:
Improvebinding lifetimeVSAvoidsecurity against replay attacks
Core Design Contradiction:
Duration of action of moving objectVSReliability

Solution Approach 1:

The system performs preliminary actions by setting the 'Used' field to a predetermined value when the binding lifetime is 0 and the nonce is valid, before any potential replay attack can occur. This pre-marking of the binding entry enables the correspondent node to detect and prevent replay attacks in subsequent binding update messages.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system implements feedback by sending a reauthentication command message to the mobile node when a binding entry with the same HoA and CoA is detected and the 'Used' field corresponds to the predetermined value. This feedback mechanism ensures that the mobile node reauthenticates before allowing the binding update to proceed, preventing replay attacks.

Inventive Principle:
Principle #23Feedback

2Reliability

If the system checks for replay attacks by examining binding entries, then security is improved, but the complexity of the binding updating process increases

Engineering Contradiction:
Improvesecurity against replay attacksVSAvoidbinding updating control operation
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The system segments the binding entry into distinct fields, including the 'Used' field that specifically indicates whether the binding entry has been marked for replay prevention. This segmentation allows the correspondent node to efficiently check for replay attacks by examining only the relevant fields (HoA, CoA, and 'Used' field) without processing the entire binding update message in detail.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system changes the parameter state by setting the 'Used' field to a predetermined value when the binding lifetime is 0 and the nonce is valid. This parameter change enables the system to distinguish between legitimate binding updates and potential replay attacks, allowing for efficient security checking without significantly increasing the overall complexity of the binding updating process.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS7764949B2Method of preventing replay attack in mobile IPv6
Publication Date: 2010.07.27 SAMSUNG ELECTRONICS CO LTD
  • US7764949B2 patent drawing
  • US7764949B2 patent drawing
  • US7764949B2 patent drawing

AI summary

Disclosed is a method of preventing a replay attack during a handoff in a communication system using a Mobile IPv6 protocol. A mobile node creates a CoA (Care of Address) by handoff and sends the CoA to a correspondent node, thereby creating a binding entry. Upon receipt of a binding update message including a HoA and a CoA from the mobile node or an attacker, the correspondent node searches a binding cache for a binding entry having the same HoA (Home Address) and CoA as included in the binding update message. If it is determined that the binding entry has the same respective HoA and CoA as contained in the binding update message, the correspondent node checks a Used field of the binding entry. If it is determined that the Used field of the binding entry is equal to a predetermined value, the correspondent node sends a reauthentication command message to the mobile node.