-
Notifications
You must be signed in to change notification settings - Fork 269
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
NULL pointer dereference get_ipv6_l4proto() #536
Labels
Comments
CVE-2019-8377 was assigned for this issue. |
GabrielGanne
added a commit
to GabrielGanne/tcpreplay
that referenced
this issue
Mar 6, 2019
Both get_ipv6_next() and get_layer4_v6() return NULL on malformed packets. Make get_layer4_v6() forward the NULL return value of get_ipv6_next() on malformed packets. This should fix issues appneta#536
GabrielGanne
added a commit
to GabrielGanne/tcpreplay
that referenced
this issue
Mar 6, 2019
get_ipv6_next() returns NULL on malformed packets. If that happens return the last header that could be read. This should fix issue appneta#536
Merged
fklassen
added a commit
that referenced
this issue
Mar 12, 2019
fklassen
added a commit
that referenced
this issue
Mar 12, 2019
GabrielGanne
added a commit
to GabrielGanne/tcpreplay
that referenced
this issue
May 2, 2019
get_ipv6_next() returns NULL on malformed packets. If that happens return the last header that could be read. This should fix issue appneta#536
GabrielGanne
pushed a commit
to GabrielGanne/tcpreplay
that referenced
this issue
May 2, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description - we observed a NULL pointer dereference occured in function
get_ipv6_l4proto()
located atget.c
.The same be triggered by sending a crafted pcap file to the tcpreplay-edit binary. It allows an attacker to cause Denial of Service (Segmentation fault) or possibly have unspecified other impact.Command - tcpreplay-edit -r 80:84 -s 20 -b -C -m 1500 -P --oneatatime -i $INTERFACE $POC
POC - REPRODUCER
Debug -
GDB -
The text was updated successfully, but these errors were encountered: