Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: handle linkstate decoding error #1743

Merged

Conversation

wyfo
Copy link
Contributor

@wyfo wyfo commented Jan 28, 2025

Panicking here was causing a major security breach concerning every non-encrypted transport, especially UDP ones. An attacker could simply forge a invalid OAM linkstate message to make the transport panic. Regarding UDP multicast network, a single message could make the whole network instantly unresponsive.

Panicking here was causing a major security breach concerning every
non-encrypted transport, especially UDP ones. An attacker could simply
forge a invalid OAM linkstate message to make the transport panic.
Regarding UDP multicast network, a single message could make the whole
network instantly unresponsive.
Copy link

PR missing one of the required labels: {'documentation', 'dependencies', 'new feature', 'bug', 'breaking-change', 'enhancement', 'internal'}

@wyfo wyfo added the bug Something isn't working label Jan 28, 2025
@Mallets
Copy link
Member

Mallets commented Jan 29, 2025

The problem is also present in case of encrypted transports. Besides that LGTM.

@Mallets Mallets merged commit 1b918b1 into eclipse-zenoh:main Jan 29, 2025
14 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants