https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4975
Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeff.morriss.ws@xxxxxxxxx
--- Comment #7 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2010-07-06 07:15:41 PDT ---
This code sequence:
ops = tvb_get_ntohl(tvb, offset+0);
op_summary=g_malloc(sizeof(nfsv4_operation_summary) * ops);
causes Wireshark to crash on fuzzed capture files (see bug 4976).
Is there some reasonable upper limit to the number of operations in a packet
(to keep us from requesting more memory than is available)?
I have a patch coded for this using 128 as the max number of operations, but I
wanted to check if the number is reasonable or not before checking it in...
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.