Security: Fix buffer overflow in src/isotp/send.c isotp_send_single_frame #26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
A critical buffer overflow vulnerability exists in
isotp_send_single_frame
function with no size validation whatsoever. This is more severe than the recent Zephyr RTOS CVE, which at least had debug-time assertions.Zephyr CVE Reference
Zephyr RTOS had the exact same vulnerability pattern that was recently patched:
https://nvd.nist.gov/vuln/detail/CVE-2023-3725
GHSA-2g3m-p6c7-8rr3
Before (vulnerable):
After (Fixed):
Affected Code in openxc/isotp-c
File:
src/isotp/send.c
Function:
isotp_send_single_frame
Vulnerability Details
Impact
Recommended Fix
Priority
High - Same pattern that warranted CVE in Zephyr RTOS
PoC
Due to the complexity of setting up a CAN hardware environment, I haven't tested this vulnerability against a real embedded system.
However, code analysis clearly demonstrates the buffer overflow potential.