Closed
Bug 544875
Opened 15 years ago
Closed 13 years ago
Investigate mNavigator usage in nsPluginArray and nsMimeTypeArray
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: smaug, Unassigned)
References
Details
(Whiteboard: [sg:audit])
Using raw pointers is scary!
Updated•15 years ago
|
Whiteboard: [sg:investigate]
Updated•15 years ago
|
Whiteboard: [sg:investigate] → [sg:audit]
Comment 1•14 years ago
|
||
Apparently it is, Sergey Glazunov found at least one sg:critical bug in that code. Is that the only problem there or are there more?
Depends on: 584517
Updated•14 years ago
|
Comment 2•14 years ago
|
||
We need this "fixed" this round to make sure bug 584517 is the only problem in there. Otherwise we're just pissing away bounties as people file them one-by-one.
blocking1.9.1: --- → .12+
blocking1.9.2: --- → .9+
blocking2.0: --- → ?
status1.9.1:
--- → wanted
status1.9.2:
--- → wanted
Is there any plans to do this audit before code-freeze this Thursday? I'm going to remove blocking as we wouldn't block shipping on this audit...
blocking1.9.1: .12+ → ---
blocking1.9.2: .9+ → ---
Reporter | ||
Comment 4•14 years ago
|
||
I could try to audit this tomorrow, if I find a nice solution for Bug 585815
today.
Comment 5•14 years ago
|
||
For what it's worth, I looked into this for the patch in bug 584512 . That's why that patch touches the mime type array as well as the plugin array. I'd appreciate smaug double-checking my work though!
Reporter | ||
Comment 6•14 years ago
|
||
Without looking at Bug 584512 I found the same bug, but not anything else.
Updated•14 years ago
|
blocking2.0: ? → -
Seems like Blake and Olli are both saying they looked into this. Can we call this fixed, that being the case? Also, can we open this up as there is no specific vulnerability discussed?
Comment 8•13 years ago
|
||
Yes.
Group: core-security
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•