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

Security: Malfunction in function l2_packet_receive_timeout() #5629

Open
UVScan opened this issue Sep 2, 2022 · 0 comments
Open

Security: Malfunction in function l2_packet_receive_timeout() #5629

UVScan opened this issue Sep 2, 2022 · 0 comments
Assignees

Comments

@UVScan
Copy link

UVScan commented Sep 2, 2022

Affected components

affected source code file: external/wpa_supplicant/src/l2_packet/l2_packet_pcap.c

Attack vector(s)

Lacking a check for the return value of pcap_dispatch.
pcap_dispatch() returns the number of packets processed on success; this can be 0 if no packets were read from a live capture (if, for example, they were discarded because they didn't pass the packet filter, or if, on platforms that support a read timeout that starts before any packets arrive, the timeout expires before any packets arrive, or if the file descriptor for the capture device is in non-blocking mode and no packets were available to be read) or if no more packets are available in a ''savefile.'' It returns -1 if an error occurs or -2 if the loop terminated due to a call to pcap_breakloop() before any packets were processed. If your application uses pcap_breakloop(), make sure that you explicitly check for -1 and -2, rather than just checking for a return value < 0.

Suggested description of the vulnerability for use in the CVE

Malfunction vulnerability in l2_packet_receive_timeout() function in Samsung Electronics TizenRT latest version (and earlier) due to missing a check on the return value of pcap_dispatch().

Discoverer(s)/Credits

UVScan

Reference(s)

https://linux.die.net/man/3/pcap_dispatch

pcap_dispatch(pcap, 10, l2_packet_receive_cb, (u_char *)l2);

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants