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

Jump to bottom

ISNs for TCP connections not sufficiently random #6

Closed
silabs-steveegerter opened this issue Nov 30, 2020 · 0 comments · Fixed by #25
Closed

ISNs for TCP connections not sufficiently random #6

silabs-steveegerter opened this issue Nov 30, 2020 · 0 comments · Fixed by #25
Assignees
@yasosa305

Comments

@silabs-steveegerter
Copy link

Initial sequence numbers (ISNs) are not derived from a sufficiently random source which could lead to an attacker either hijacking an existing connection or spoofing future connections. ISNs should adhere to RFC6528 to be more secure. ISNs are retrieved by NetUtil_InitSeqNbrGet().
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yasosa305 yasosa305

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Added code that allows the user to randomize initial sequence numbers… weston-embedded/uC-TCP-IP
3 participants
@silabs-steveegerter @yasosa305 @wes-jmagasrevy