-
Notifications
You must be signed in to change notification settings - Fork 274
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
[Bug]heap-buffer-overflow in tcpprep with MemcmpInterceptorCommon() #616
Comments
The test logic on datalen was inverted. Processing truncated packats should now raise a warning like the following: Warning: <pcap> was captured using a snaplen of 4 bytes. This may mean you have truncated packets. Fixes appneta#616 appneta#617 Signed-off-by: Gabriel Ganne <gabriel.ganne@gmail.com>
CVE-2020-24265 go assigned for this issue. |
Excuse my bluntness, wouldn't it be sufficient to check whether there's enough data before accessing it, in other words:
|
Ooops, the previous comment should have gone to #617 For this one, suggestion is likewise:
Did I miss the point? |
@cbiedl thanks for the feedback. I plan to schedule some time in the next 2 weeks to address this and other issues. |
@fklassen Any updates? |
Had a backlog of work so took some vacation to address this and a few other critical bugs. |
Also did some fixes to Juniper Ethernet protocols to fix some bugs and support various types of Juniper Ethernet protocol types. Used Wireshark sources to figure out all the different packet types that Juniper uses. Unable to test all types because of lack of JNPER DLT pcaps. Also applied a fix for DLT_RAW to prevent similar issues.
Bug #616 Add checks for datalen for DLT_JUNIPER_ETHER
Adde checks for Also did some fixes to Juniper Ethernet protocols to fix some bugs Unable to test all types because of lack of JNPER DLT pcaps. Also applied a fix for DLT_RAW to prevent similar issues. |
Bluntness excepted. Juniper protocol has very little testing available because I have a lack of PCAP files available. I have never seen the PCAP files that were used to create this feature. I am fixing base on looking at Wireshark decodes. |
Bug #616 Bug_#617_CVE-2020-24265 includes updates that fixes this issue. See PR #637 for details.
From mail lists: Hi, The following vulnerability was published for tcpreplay. CVE-2020-24265[0]: If you fix the vulnerability please also make sure to include the For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2020-24265 Please adjust the affected versions in the BTS as needed. Regards, |
What's the problem (or question)?
A heap buffer overflow with MemcmpInterceptorCommon() in the 4.3.3 version of tcpprep.
Steps to reproduce the behavior:
poc_tcpprep_heap_buffer_overflow_MemcmpInterceptorCommon.tar.gz
Expected behavior
Get an a.cach at the path or exit when meet abnormal input.
System :
Additional context
none.
The text was updated successfully, but these errors were encountered: