Communication Message Freshness Validation for Replay Attack Detection

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing communication systems are vulnerable to replay attacks where attackers resend valid messages, leading to incorrect reception and potential security breaches, especially in shared bus systems like CAN, CAN FD, or CAN XL, due to re-sorting of messages based on priority.

Innovation Solution

Implementing a freshness value system with a defined freshness window and historical log to validate message timeliness, ensuring only messages within a specific timeliness range are accepted, and tracking previously received messages to detect replay attacks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a freshness value system with freshness window and historical log is implemented, then security against replay attacks is improved, but device complexity increases

Engineering Contradiction:
Improvesecurity against replay attacksVSAvoidcomplexity of freshness value management
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The freshness value management is segmented into two distinct subsets: a first subset for possible current freshness values within a defined window, and a second subset for historical freshness values. This segmentation allows the system to efficiently distinguish between valid fresh messages and replayed old messages without requiring complex analysis of all possible message histories.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The system pre-defines a freshness window containing a set of possible current freshness values before message reception. When a message is received, the system only needs to check whether the message's freshness value falls within this pre-defined window or matches any historical values, rather than performing complex real-time analysis of message timeliness from scratch.

Inventive Principle:
Principle #10Preliminary action

2Productivity

If message re-sorting based on priority is implemented in shared bus systems, then message transmission efficiency is improved, but vulnerability to replay attacks increases

Engineering Contradiction:
Improvemessage transmission efficiencyVSAvoidvulnerability to replay attacks
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system incorporates feedback mechanisms by maintaining a historical subset of previously received freshness values and comparing incoming message freshness values against both the current window and historical records. This feedback loop enables the system to detect replayed messages even when they arrive after priority-based re-sorting, thus maintaining security without sacrificing transmission efficiency.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system changes the parameter used for message validation from simple timeliness checking to a two-parameter approach: checking whether the freshness value is within the current window and whether it matches any historical values. This parameter change allows the system to maintain priority-based re-sorting efficiency while adding replay protection.

Inventive Principle:
Principle #35Parameter changes

3Device complexity

If only one priority ID is allowed per group, then replay attack detection is simplified, but system adaptability decreases

Engineering Contradiction:
Improvesimplicity of replay detectionVSAvoidpriority ID configuration flexibility
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The system dynamically manages multiple priority IDs within each group by maintaining a freshness window that adapts to the current message sequence and a historical subset that tracks seen values. This dynamic approach allows the system to handle multiple priority levels while maintaining replay detection capability, eliminating the need for static single-priority-ID configurations.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS20250274460A1Method and device for processing data associated with a communication system
Publication Date: 2025.08.28 ROBERT BOSCH GMBH
  • US20250274460A1 patent drawing
  • US20250274460A1 patent drawing
  • US20250274460A1 patent drawing

AI summary

A method for processing data associated with a communication system. The method includes: managing a set of, for example, one or more, values for a first parameter which characterizes a timeliness of a message that can be received via the communication system, wherein for example, the set has at least one first subset that has, for example one or more, possible values for the first parameter and at least one second subset that has, for example one or more, historical values for the first parameter, evaluating a parameter value of the received message characterizing a timeliness of a message received via the communication system based on the set.