-
Notifications
You must be signed in to change notification settings - Fork 285
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 deref crash in m_copydata #351
Labels
Comments
Hey @markwo, I'm interested in your fuzzer code. We're already fuzzing our project with libfuzz and are preparing it for OSS-FUZZ integration. Please send an email to weinrank@fh-muenster.de best regards |
Can be reproduced with the following packetdrill script:
|
Closed
tuexen
added a commit
that referenced
this issue
Sep 1, 2019
This fixes problem with parameters indicating a zero length or partial parameters after an unknown parameter indicating to stop processing. It also fixes a problem with state cookie parameters after unknown parametes indicating to stop porcessing. Thanks to Mark Wodrich from Google for finding two of these issues by fuzz testing the userland stack and reporting them in #351 and #352
tuexen
added a commit
to sctplab/stream-reset-improved
that referenced
this issue
Sep 1, 2019
This fixes problem with parameters indicating a zero length or partial parameters after an unknown parameter indicating to stop processing. It also fixes a problem with state cookie parameters after unknown parametes indicating to stop porcessing. Thanks to Mark Wodrich from Google for finding two of these issues by fuzz testing the userland stack and reporting them in sctplab/usrsctp#351 and sctplab/usrsctp#352
tuexen
added a commit
to sctplab/SCTP_NKE_Yosemite
that referenced
this issue
Sep 1, 2019
This fixes problem with parameters indicating a zero length or partial parameters after an unknown parameter indicating to stop processing. It also fixes a problem with state cookie parameters after unknown parametes indicating to stop porcessing. Thanks to Mark Wodrich from Google for finding two of these issues by fuzz testing the userland stack and reporting them in sctplab/usrsctp#351 and sctplab/usrsctp#352
tuexen
added a commit
to sctplab/SCTP_NKE_ElCapitan
that referenced
this issue
Sep 1, 2019
This fixes problem with parameters indicating a zero length or partial parameters after an unknown parameter indicating to stop processing. It also fixes a problem with state cookie parameters after unknown parametes indicating to stop porcessing. Thanks to Mark Wodrich from Google for finding two of these issues by fuzz testing the userland stack and reporting them in sctplab/usrsctp#351 and sctplab/usrsctp#352
tuexen
added a commit
to sctplab/SCTP_NKE_HighSierra
that referenced
this issue
Sep 1, 2019
This fixes problem with parameters indicating a zero length or partial parameters after an unknown parameter indicating to stop processing. It also fixes a problem with state cookie parameters after unknown parametes indicating to stop porcessing. Thanks to Mark Wodrich from Google for finding two of these issues by fuzz testing the userland stack and reporting them in sctplab/usrsctp#351 and sctplab/usrsctp#352
tuexen
added a commit
to sctplab/pr-sctp-improved
that referenced
this issue
Sep 1, 2019
This fixes problem with parameters indicating a zero length or partial parameters after an unknown parameter indicating to stop processing. It also fixes a problem with state cookie parameters after unknown parametes indicating to stop porcessing. Thanks to Mark Wodrich from Google for finding two of these issues by fuzz testing the userland stack and reporting them in sctplab/usrsctp#351 and sctplab/usrsctp#352
tuexen
added a commit
to sctplab/sctp-idata
that referenced
this issue
Sep 1, 2019
This fixes problem with parameters indicating a zero length or partial parameters after an unknown parameter indicating to stop processing. It also fixes a problem with state cookie parameters after unknown parametes indicating to stop porcessing. Thanks to Mark Wodrich from Google for finding two of these issues by fuzz testing the userland stack and reporting them in sctplab/usrsctp#351 and sctplab/usrsctp#352
I can confirm this fixes the issue, thanks! |
#160 (comment) Might be related to this? |
uqs
pushed a commit
to freebsd/freebsd-src
that referenced
this issue
Sep 7, 2019
Improve the handling of state cookie parameters in INIT-ACK chunks. This fixes problem with parameters indicating a zero length or partial parameters after an unknown parameter indicating to stop processing. It also fixes a problem with state cookie parameters after unknown parametes indicating to stop porcessing. Thanks to Mark Wodrich from Google for finding two of these issues by fuzz testing the userland stack and reporting them in sctplab/usrsctp#351 and sctplab/usrsctp#352
mat813
pushed a commit
to mat813/freebsd
that referenced
this issue
Sep 16, 2019
Improve the handling of state cookie parameters in INIT-ACK chunks. This fixes problem with parameters indicating a zero length or partial parameters after an unknown parameter indicating to stop processing. It also fixes a problem with state cookie parameters after unknown parametes indicating to stop porcessing. Thanks to Mark Wodrich from Google for finding two of these issues by fuzz testing the userland stack and reporting them in sctplab/usrsctp#351 and sctplab/usrsctp#352 git-svn-id: https://svn.freebsd.org/base/stable/12@352007 ccf9f872-aa2e-dd11-9fc8-001c23d0bc1f
hardenedbsd-services
pushed a commit
to HardenedBSD/hardenedBSD
that referenced
this issue
Jan 29, 2021
Improve the handling of state cookie parameters in INIT-ACK chunks. This fixes problem with parameters indicating a zero length or partial parameters after an unknown parameter indicating to stop processing. It also fixes a problem with state cookie parameters after unknown parametes indicating to stop porcessing. Thanks to Mark Wodrich from Google for finding two of these issues by fuzz testing the userland stack and reporting them in sctplab/usrsctp#351 and sctplab/usrsctp#352
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
While working on a fuzzer for usrsctp, I hit a SEGV accessing a NULL pointer. The PCAP is attached - output and stack trace of the crash are below.
I'm cleaning up the fuzzer currently - can share the code if you need it to repro. (Would also like to eventually get this fuzzer added to the repo as an OSS-Fuzz target).
null_deref.zip
The text was updated successfully, but these errors were encountered: