Closed
Bug 791270
Opened 13 years ago
Closed 13 years ago
WebRTC crash [@sipcc::PeerConnectionImpl::AddStream]
Categories
(Core :: WebRTC: Signaling, defect)
Tracking
()
VERIFIED
FIXED
mozilla19
Tracking | Status | |
---|---|---|
firefox18 | --- | affected |
People
(Reporter: posidron, Assigned: ehugg)
References
Details
(Keywords: crash, testcase, Whiteboard: [WebRTC], [blocking-webrtc+])
Attachments
(4 files)
15.23 KB,
text/plain
|
Details | |
254 bytes,
text/html
|
Details | |
1.27 KB,
patch
|
jesup
:
review+
|
Details | Diff | Splinter Review |
1.92 KB,
patch
|
jesup
:
review+
|
Details | Diff | Splinter Review |
The parameter of addStream() is not properly validated.
Reporter | ||
Comment 1•13 years ago
|
||
Updated•13 years ago
|
Whiteboard: [WebRTC], [blocking-webrtc+]
Reporter | ||
Updated•13 years ago
|
Blocks: fuzzing-webrtc
Assignee | ||
Comment 2•13 years ago
|
||
Assignee | ||
Comment 3•13 years ago
|
||
Comment on attachment 669728 [details] [diff] [review]
Protect AddStream from NULL input
Change assert on null input to AddStream to be a runtime failure.
Test case should be changed to mozRTCPeerConnection to test on latest.
Attachment #669728 -
Flags: review?(rjesup)
Assignee | ||
Updated•13 years ago
|
Assignee: nobody → ethanhugg
Comment 4•13 years ago
|
||
Comment on attachment 669728 [details] [diff] [review]
Protect AddStream from NULL input
Review of attachment 669728 [details] [diff] [review]:
-----------------------------------------------------------------
Since xpconnect already throws an exception when we return an error here, r+
Attachment #669728 -
Flags: review?(rjesup) → review+
Comment 5•13 years ago
|
||
Assignee | ||
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Comment 6•13 years ago
|
||
Has this been landed for Firefox 18? Please set the TM accordingly. Thanks.
Comment 7•13 years ago
|
||
Landed for 19, and we should consider for uplift to 18
Target Milestone: --- → mozilla19
Updated•13 years ago
|
status-firefox18:
--- → affected
Comment 9•13 years ago
|
||
Updated•13 years ago
|
Flags: in-testsuite?
Comment 10•13 years ago
|
||
If this patch fixes the crash completely the following try run should be successful: https://tbpl.mozilla.org/?tree=Try&rev=da75e3bd42d9
Once the patch has been reviewed and we are green we are good to land on m-c.
Attachment #671657 -
Flags: review?(rjesup)
Comment 11•13 years ago
|
||
(In reply to Henrik Skupin (:whimboo) from comment #10)
> Created attachment 671657 [details] [diff] [review]
> Crashtest v1
>
> If this patch fixes the crash completely the following try run should be
> successful: https://tbpl.mozilla.org/?tree=Try&rev=da75e3bd42d9
>
> Once the patch has been reviewed and we are green we are good to land on m-c.
If the try run passes, can mark this as verified?
Comment 12•13 years ago
|
||
(In reply to Jason Smith [:jsmith] from comment #11)
> (In reply to Henrik Skupin (:whimboo) from comment #10)
> > Created attachment 671657 [details] [diff] [review]
> > Crashtest v1
> >
> > If this patch fixes the crash completely the following try run should be
> > successful: https://tbpl.mozilla.org/?tree=Try&rev=da75e3bd42d9
> >
> > Once the patch has been reviewed and we are green we are good to land on m-c.
>
> If the try run passes, can mark this as verified?
Actually, change that. I just ran the attached test case and it looked alright.
Comment 13•13 years ago
|
||
Wait a second, didn't test this right.
Comment 14•13 years ago
|
||
Now I did this right this time. Looks good.
Status: RESOLVED → VERIFIED
Keywords: verifyme
Updated•13 years ago
|
Attachment #671657 -
Flags: review?(rjesup) → review+
Comment 15•13 years ago
|
||
Comment 16•13 years ago
|
||
Flags: in-testsuite? → in-testsuite+
You need to log in
before you can comment on or make changes to this bug.
Description
•