Closed Bug 1429216 Opened 7 years ago Closed 7 years ago

UAF due to webrtc codec init failure

Categories

(Core :: WebRTC, defect, P1)

58 Branch
Unspecified
macOS
defect

Tracking

()

RESOLVED FIXED
mozilla59
Tracking Status
firefox-esr52 --- unaffected
firefox58 --- fixed
firefox59 --- fixed

People

(Reporter: jesup, Assigned: jesup)

References

()

Details

(Keywords: crash, csectype-uaf, sec-high)

Crash Data

Attachments

(1 file, 1 obsolete file)

+++ This bug was initially created as a clone of Bug #1426449 +++ If InitEncode() fails, in non-debug builds, a race is set up where a pending OnBitrateUpdated will try to access the temporal_layers_, which failure of SetSendCodec() will cause to be deleted before OnBitrateUpdated runs. This causes a UAF. Also, generally clean up and exit on failure. InitEncode shouldn't fail -- but if it does (and there are a lot of ways it can), we should handle it smoothly.
works fine if I force the InitEncode to fail now
Attachment #8941199 - Flags: review?(drno)
forgot to include the .h file
Attachment #8941201 - Flags: review?(drno)
Attachment #8941199 - Attachment is obsolete: true
Attachment #8941199 - Flags: review?(drno)
Comment on attachment 8941201 [details] [diff] [review] handle RegisterSendCodec() failure better in non-debug builds Review of attachment 8941201 [details] [diff] [review]: ----------------------------------------------------------------- LGTM
Attachment #8941201 - Flags: review?(drno) → review+
Randell is this something we would want to upstream?
Flags: needinfo?(rjesup)
Yes, though there are probably cleaner ways to do with (with larger changes), so they may not want to take it as-is - but that's up to them; we should put it up. Note: this is a sec issue. We should try to coordinate this with Google, though they don't seem to handle sec issues in the webrtc code in the same way we do.
Flags: needinfo?(rjesup) → needinfo?(dminor)
Sec and beta requests are in bug 1426449
Flags: needinfo?(dminor)
Rank: 9
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Group: media-core-security → core-security-release
Target Milestone: --- → mozilla59
Group: core-security-release
Type: enhancement → defect
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: