Skip to content

🛡️ Sentinel: [CRITICAL] Fix buffer overflows in EAD protocol handlers#38

Open
ManupaKDU wants to merge 1 commit intomainfrom
sentinel-ead-bounds-check-703436063192267359
Open

🛡️ Sentinel: [CRITICAL] Fix buffer overflows in EAD protocol handlers#38
ManupaKDU wants to merge 1 commit intomainfrom
sentinel-ead-bounds-check-703436063192267359

Conversation

@ManupaKDU
Copy link
Copy Markdown

🛡️ Sentinel: [CRITICAL] Fix buffer overflows in EAD protocol handlers

🚨 Severity: CRITICAL
💡 Vulnerability: EAD service (ead.c) and client (ead-client.c) lacked strict bounds checking when processing payload lengths from network packets.
🎯 Impact: Attackers could send malformed UDP packets with modified length fields that underflow to negative values or exceed allocated boundaries, leading to out-of-bounds array writes and memcpy heap overflows (DoS/RCE).
🔧 Fix: Added explicit boundaries verifying msg->len calculations are both > 0 and < sizeof(buffer) prior to data extraction.
✅ Verification: Compiled successfully using make -C package/network/services/ead/src.


PR created automatically by Jules for task 703436063192267359 started by @manupawickramasinghe

Explicitly bounds-check the lengths of decrypted network payloads
against the underlying buffer sizes to prevent stack and heap
overflows. Ensures length calculations from packets do not underflow
into negative sizes causing `memcpy` faults.

Signed-off-by: Jules Agent <jules@example.com>

Co-authored-by: manupawickramasinghe <73810867+manupawickramasinghe@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment