pith. sign in

arxiv: 2604.11853 · v1 · submitted 2026-04-13 · 💻 cs.CR

Evaluating Lightweight Block Cipher Payload Encryption for Real-Time CAN Traffic

Kevin Setterstrom , Jeremy Straub This is my paper

Pith reviewed 2026-05-10 16:26 UTC · model grok-4.3

classification 💻 cs.CR
keywords CANlightweight block cipherpayload encryptionreverse engineeringreal-time embedded systemssignal inferencebus security
0
0 comments X

The pith

Lightweight block cipher encryption masks CAN signal semantics on microcontrollers with minimal timing cost

A machine-rendered reading of the paper's core claim, the machinery that carries it, and where it could break.

The paper examines whether encrypting CAN bus messages with a lightweight block cipher can stop attackers from deducing signal meanings through observation and statistics. Experiments on a QT PY ESP32-S2 board measure how encryption affects transmission timing, hides payload patterns, and blocks correlation-based inferences. Results show that the encryption hides constants and predictable patterns without disrupting a 100 Hz schedule. This approach offers a practical way to protect vehicle and industrial network data on low-cost hardware where full encryption might be too slow.

Core claim

Applying a lightweight block cipher to encrypt CAN payloads prevents semantic taxonomy-based reverse engineering by eliminating observable constant values and predictable signal patterns. The method maintains real-time performance at 100 Hz on an ESP32-S2 microcontroller, with only limited impact on timing.

What carries the argument

Lightweight block cipher encryption of CAN payloads on embedded real-time controllers

If this is right

  • Encryption masks constant values and predictable signal patterns in the payloads.
  • The 100 Hz transmission schedule remains intact on the tested hardware.
  • Timing overhead stays low enough for real-time CAN operation.
  • Passive inference of signal semantics is reduced on resource-constrained devices.

Where Pith is reading between the lines

These are editorial extensions of the paper, not claims the author makes directly.

  • Similar encryption might protect other bus protocols like LIN or FlexRay in vehicles if timing constraints match.
  • Testing against machine learning based inference attacks would show if the masking holds for advanced analysis.
  • The approach could be combined with key management schemes for deployment in production systems.

Load-bearing premise

Semantic taxonomy-based reverse engineering depends primarily on constant values and predictable patterns in unencrypted CAN payloads that can be masked by block cipher encryption.

What would settle it

Demonstrating successful inference of signal semantics from the encrypted CAN traffic using statistical or observational methods would show the encryption does not prevent reverse engineering.

read the original abstract

This study evaluates the feasibility of integrating lightweight block cipher payload encryption into a real-time embedded controller area network (CAN) node using a QT PY ESP32-S2 microcontroller. This work seeks to determine whether the use of a block cipher can prevent semantic taxonomy-based reverse engineering, which infers signal meaning from unencrypted CAN traffic using observation and statistical analysis. CAN payloads are encrypted using a lightweight block cipher and evaluated through experiments that measure timing impact, payload pattern observability, and correlation-based inference. Results indicate that encryption masks constant values and predictable signal patterns while preserving a 100 Hz transmission schedule. These findings suggest that lightweight payload encryption can reduce passive, observation based inference of CAN signal semantics on resource-constrained hardware with limited timing overhead impact.

Editorial analysis

A structured set of objections, weighed in public.

Desk editor's note, referee report, simulated authors' rebuttal, and a circularity audit. Tearing a paper down is the easy half of reading it; the pith above is the substance, this is the friction.

Referee Report

2 major / 1 minor

Summary. The manuscript evaluates the feasibility of integrating lightweight block cipher payload encryption into a real-time CAN node on a QT PY ESP32-S2 microcontroller. It aims to determine if encryption can prevent semantic taxonomy-based reverse engineering of CAN signals via observation and statistical analysis. Experiments measure timing impact, payload pattern observability, and correlation-based inference, with the conclusion that encryption masks constant values and predictable patterns while preserving a 100 Hz schedule and imposing limited overhead.

Significance. If the central claims hold, the work would provide practical evidence that lightweight encryption can be deployed on resource-constrained embedded hardware to reduce passive inference attacks on CAN traffic without violating real-time constraints. The use of actual microcontroller hardware and focus on measurable timing and observability metrics are strengths that ground the evaluation in a realistic setting.

major comments (2)
  1. [Abstract] Abstract: The claim that encryption 'masks constant values and predictable signal patterns' is load-bearing for the central thesis but is not supported by the described experiments. Because the block cipher is deterministic with a fixed key, identical plaintext bytes (including constants in signals) produce identical ciphertexts, preserving structural features such as zero-variance byte positions and repeating blocks that taxonomy-based or correlation-based inference can exploit without recovering plaintext semantics.
  2. [Results] Results / Evaluation section: No quantitative results, error bars, baseline comparisons (e.g., unencrypted vs. encrypted inference success rates), or detailed methodology (cipher choice, key schedule, exact pattern metrics) are provided, leaving the statements about reduced observability and limited timing impact unverifiable and without statistical support.
minor comments (1)
  1. [Abstract] The abstract and introduction would benefit from explicitly naming the lightweight block cipher employed and the key management approach used in the experiments.

Simulated Author's Rebuttal

2 responses · 0 unresolved

We thank the referee for the constructive feedback on our manuscript. We have addressed each major comment point by point below, providing clarifications and making revisions to improve precision and support for the claims.

read point-by-point responses

  1. Referee: [Abstract] Abstract: The claim that encryption 'masks constant values and predictable signal patterns' is load-bearing for the central thesis but is not supported by the described experiments. Because the block cipher is deterministic with a fixed key, identical plaintext bytes (including constants in signals) produce identical ciphertexts, preserving structural features such as zero-variance byte positions and repeating blocks that taxonomy-based or correlation-based inference can exploit without recovering plaintext semantics.

    Authors: We agree that a deterministic block cipher with a fixed key will map identical plaintexts to identical ciphertexts, preserving certain structural features such as constant byte positions. Our original phrasing intended to convey that semantic content and predictable variations (which enable taxonomy-based inference of signal meaning) are masked, as the ciphertext values no longer correlate with the original signal semantics or physical interpretations. We have revised the abstract to clarify this distinction, explicitly noting the preservation of structural invariants while emphasizing the reduction in semantic observability. Additional discussion of these limitations has been incorporated into the manuscript. revision: yes

  2. Referee: [Results] Results / Evaluation section: No quantitative results, error bars, baseline comparisons (e.g., unencrypted vs. encrypted inference success rates), or detailed methodology (cipher choice, key schedule, exact pattern metrics) are provided, leaving the statements about reduced observability and limited timing impact unverifiable and without statistical support.

    Authors: We have expanded the Results and Evaluation sections to include the requested quantitative details. This now incorporates timing measurements with error bars from repeated trials on the QT PY ESP32-S2, baseline comparisons of inference success rates between unencrypted and encrypted traffic using the taxonomy-based method, and full methodology specifying the lightweight block cipher, key schedule, and pattern metrics (e.g., byte variance and autocorrelation). These additions make the claims on observability and timing impact verifiable with statistical support. revision: yes

Circularity Check

0 steps flagged

No significant circularity in empirical evaluation

full rationale

The paper reports direct hardware experiments on an ESP32-S2 microcontroller measuring timing overhead, payload pattern observability after encryption, and resistance to correlation-based inference attacks. No mathematical derivations, parameter fittings to data subsets, predictions that reduce to inputs by construction, or load-bearing self-citations are present. The central claims rest on experimental outcomes rather than any self-referential logic or renamed known results, rendering the analysis self-contained.

Axiom & Free-Parameter Ledger

0 free parameters · 1 axioms · 0 invented entities

The claim rests on the domain assumption that attackers use statistical analysis of unencrypted patterns and that the chosen lightweight cipher sufficiently disrupts those patterns without introducing new entities or fitted parameters.

axioms (1)
  • domain assumption Semantic taxonomy-based reverse engineering infers signal meaning primarily from constant values and predictable patterns in unencrypted CAN traffic.
    The paper positions encryption as a countermeasure specifically against this form of inference.

pith-pipeline@v0.9.0 · 5413 in / 1136 out tokens · 40961 ms · 2026-05-10T16:26:50.609664+00:00 · methodology

discussion (0)

Sign in with ORCID, Apple, or X to comment. Anyone can read and Pith papers without signing in.

Reference graph

Works this paper leans on

24 extracted references · 24 canonical work pages

  1. [1]

    A Survey of Remote Automotive Attack Surfaces,

    C. Miller and C. Valasek, “A Survey of Remote Automotive Attack Surfaces,” Defcon 22, 2014

    work page 2014

  2. [2]

    Adventures in Automotive Networks and Control Units,

    C. Valasek and C. Miller, “Adventures in Automotive Networks and Control Units,” Technical White Paper, 2013

    work page 2013

  3. [3]

    Remote Exploitation of an Unaltered Passenger Vehicle,

    C. Miller and C. Valasek, “Remote Exploitation of an Unaltered Passenger Vehicle,” Defcon 23, vol. 2015, 2015

    work page 2015

  4. [4]

    READ: Reverse engineering of automotive data frames,

    M. Marchetti and D. Stabili, “READ: Reverse engineering of automotive data frames,” IEEE Transactions on Information Forensics and Security, vol. 14, no. 4, 2019, doi: 10.1109/TIFS.2018.2870826

    work page doi:10.1109/tifs.2018.2870826 2019

  5. [5]

    Analysis of the Efficacy of the Use of Inertial Measurement and Global Positioning System Data to Reverse Engineer Automotive CAN Bus Steering Signals,

    K. Setterstrom and J. Straub, “Analysis of the Efficacy of the Use of Inertial Measurement and Global Positioning System Data to Reverse Engineer Automotive CAN Bus Steering Signals,” 2024

    work page 2024

  6. [6]

    Development of an Autonomous Reverse Engineering Capability for Controller Area Network Messages to Support Autonomous Control Retrofits,

    K. Setterstrom and J. Straub, “Development of an Autonomous Reverse Engineering Capability for Controller Area Network Messages to Support Autonomous Control Retrofits,” 2023

    work page 2023

  7. [7]

    Trade-off analysis of safety and security in CAN bus communication,

    L. Dariz, M. Selvatici, M. Ruggeri, G. Costantino, and F. Martinelli, “Trade-off analysis of safety and security in CAN bus communication,” in 2017 5th IEEE International Conference on Models and Technologies for Intelligent Transportation Systems (MT-ITS), 2017, pp. 226–231. doi: 10.1109/MTITS.2017.8005670

    work page doi:10.1109/mtits.2017.8005670 2017

  8. [8]

    The SIMON and SPECK lightweight block ciphers,

    R. Beaulieu, S. Treatman-Clark, D. Shors, B. Weeks, J. Smith, and L. Wingers, “The SIMON and SPECK lightweight block ciphers,” in Proceedings - Design Automation Conference, Institute of Electrical and Electronics Engineers Inc., Jul. 2015. doi: 10.1145/2744769.2747946

    work page doi:10.1145/2744769.2747946 2015

  9. [9]

    Using of tiny encryption algorithm in CAN-Bus communication,

    M. Jukl and J. Čupera, “Using of tiny encryption algorithm in CAN-Bus communication,” Research in Agricultural Engineering, vol. 62, no. 2, pp. 50–55, 2016, doi: 10.17221/12/2015-RAE

    work page doi:10.17221/12/2015-rae 2016

  10. [10]

    A review of lightweight block ciphers,

    G. Hatzivasilis, K. Fysarakis, I. Papaefstathiou, and C. Manifavas, “A review of lightweight block ciphers,” Jun. 01, 2018, Springer Verlag. doi: 10.1007/s13389-017- 0160-y

    work page doi:10.1007/s13389-017- 2018

  11. [11]

    Arduino Cryptography Library: SpeckSmall Class Reference

    “Arduino Cryptography Library: SpeckSmall Class Reference.” Accessed: May 10, 2024. [Online]. Available: https://rweather.github.io/arduinolibs/classSpeckSmall.html

    work page 2024

  12. [12]

    The application of controller area network on vehicle,

    W. Xing, H. Chen, and H. Ding, “The application of controller area network on vehicle,” in Proceedings of the IEEE International Vehicle Electronics Conference (IVEC’99) (Cat. No.99EX257), 1999, pp. 455–458 vol.1. doi: 10.1109/IVEC.1999.830728

    work page doi:10.1109/ivec.1999.830728 1999

  13. [13]

    Vehicle Applications of Controller Area Network,

    K. Johansson, M. Törngren, and L. Nielsen, “Vehicle Applications of Controller Area Network,” 2005, pp. 741–765. doi: 10.1007/0-8176-4404-0_32

    work page doi:10.1007/0-8176-4404-0_32 2005

  14. [14]

    Robust control of a throttle body for drive by wire operation of automotive engines,

    C. Rossi, A. Tilli, and A. Tonielli, “Robust control of a throttle body for drive by wire operation of automotive engines,” IEEE Transactions on Control Systems Technology, vol. 8, no. 6, 2000, doi: 10.1109/87.880604

    work page doi:10.1109/87.880604 2000

  15. [15]

    An Overview of Drive by Wire Technology for Automobiles,

    A. Goyal and A. Thakur, “An Overview of Drive by Wire Technology for Automobiles,” in 2019 International Conference on Automation, Computational and Technology Management (ICACTM), 2019, pp. 108–110. doi: 10.1109/ICACTM.2019.8776712

    work page doi:10.1109/icactm.2019.8776712 2019

  16. [16]

    ECU software updating in future vehicle networks,

    Y. Onuma, Y. Terashima, and R. Kiyohara, “ECU software updating in future vehicle networks,” in Proceedings - 31st IEEE International Conference on Advanced Information Networking and Applications Workshops, WAINA 2017, 2017. doi: 10.1109/WAINA.2017.45

    work page doi:10.1109/waina.2017.45 2017

  17. [17]

    National Instruments CAN Overview,

    National Instruments, “National Instruments CAN Overview,” https://www.ni.com/en- us/innovations/white-papers/06/controller-area-network--can--overview.html

    work page

  18. [18]

    Introduction to the Controller Area Network ( CAN ),

    S. Corrigan and I. Interface, “Introduction to the Controller Area Network ( CAN ),” Texas Instruments, no. August 2002, pp. 1–17, 2016

    work page 2002

  19. [19]

    Evaluation of CAN Bus Security Vulnerabilities and Potential Solutions,

    A. Alfardus and D. B. Rawat, “Evaluation of CAN Bus Security Vulnerabilities and Potential Solutions,” in 2023 Sixth International Conference of Women in Data Science at Prince Sultan University (WiDS PSU), 2023, pp. 90–97. doi: 10.1109/WiDS- PSU57071.2023.00030

    work page doi:10.1109/wids- 2023

  20. [20]

    CANAuth - A Simple, Backward Compatible Broadcast Authentication Protocol for CAN bus,

    A. Herrewege, D. Singelée, and I. Verbauwhede, “CANAuth - A Simple, Backward Compatible Broadcast Authentication Protocol for CAN bus,” May 2011, p. 7

    work page 2011

  21. [21]

    Security authentication system for in-vehicle network,

    H. Ueda, R. Kurachi, H. Takada, T. Mizutani, M. Inoue, and S. Horihata, “Security authentication system for in-vehicle network,” pp. 5–9, May 2015

    work page 2015

  22. [22]

    A secure protocol for session keys establishment between ECUs in the CAN bus,

    S. Fassak, Y. El Hajjaji El Idrissi, N. Zahid, and M. Jedra, “A secure protocol for session keys establishment between ECUs in the CAN bus,” in 2017 International Conference on Wireless Networks and Mobile Communications (WINCOM), 2017, pp. 1–6. doi: 10.1109/WINCOM.2017.8238149

    work page doi:10.1109/wincom.2017.8238149 2017

  23. [23]

    A Lightweight Synchronous Cryptographic Hash Chain Solution to Securing the Vehicle CAN bus,

    J. Halabi and H. Artail, “A Lightweight Synchronous Cryptographic Hash Chain Solution to Securing the Vehicle CAN bus,” in 2018 IEEE International Multidisciplinary Conference on Engineering Technology (IMCET), 2018, pp. 1–6. doi: 10.1109/IMCET.2018.8603057

    work page doi:10.1109/imcet.2018.8603057 2018

  24. [24]

    mcp_can - Arduino Reference

    “mcp_can - Arduino Reference.” Accessed: May 10, 2024. [Online]. Available: https://www.arduino.cc/reference/en/libraries/mcp_can/

    work page 2024