Closed
Bug 1343069
Opened 7 years ago
Closed 7 years ago
Bug 1302071 added code which fails the static analysis check in 1336510
Categories
(Core :: Layout, defect)
Core
Layout
Tracking
()
RESOLVED
FIXED
mozilla54
Tracking | Status | |
---|---|---|
firefox-esr45 | --- | unaffected |
firefox51 | --- | unaffected |
firefox52 | --- | unaffected |
firefox-esr52 | --- | unaffected |
firefox53 | --- | wontfix |
firefox54 | --- | fixed |
People
(Reporter: nika, Assigned: nika)
References
Details
(Keywords: sec-high, Whiteboard: [post-critsmash-triage][adv-main54+])
Attachments
(1 file)
1.25 KB,
patch
|
mattwoodrow
:
review+
lizzard
:
approval-mozilla-aurora-
|
Details | Diff | Splinter Review |
I rebased the static analysis onto inbound as I hope to land it as soon as I uplift to beta/aurora, and noticed that a new failure had appeared due to the lambda added here: http://searchfox.org/mozilla-central/rev/4039fb4c5833706f6880763de216974e00ba096c/layout/base/nsPresContext.cpp#3271-3274. This bug blocks landing the analysis on central.
Assignee | ||
Comment 1•7 years ago
|
||
MozReview-Commit-ID: GRi4afSovP4
Attachment #8842096 -
Flags: review?(matt.woodrow)
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → michael
Updated•7 years ago
|
Attachment #8842096 -
Flags: review?(matt.woodrow) → review+
Assignee | ||
Comment 2•7 years ago
|
||
Comment on attachment 8842096 [details] [diff] [review] Capture a strong reference to nsRootPresContext in EnsureEventualDidPaintEvent [Security approval request comment] How easily could an exploit be constructed based on the patch? I imagine it would be quite difficult to exploit this bug. Do comments in the patch, the check-in comment, or tests included in the patch paint a bulls-eye on the security problem? The security problem is fairly evident from the commit message and changes made. Which older supported branches are affected by this flaw? Just nightly, but we're considering uplifting bug 1302071 which would make it affect aurora too. If not all supported branches, which bug introduced the flaw? bug 1302071 Do you have backports for the affected branches? If not, how different, hard to create, and risky will they be? There are no other affected branches. How likely is this patch to cause regressions; how much testing does it need? This is unlikely to cause regressions.
Attachment #8842096 -
Flags: sec-approval?
Comment 3•7 years ago
|
||
Comment on attachment 8842096 [details] [diff] [review] Capture a strong reference to nsRootPresContext in EnsureEventualDidPaintEvent Bugs that only affect trunk can land whenever. Fire away!
Attachment #8842096 -
Flags: sec-approval?
Assignee | ||
Comment 4•7 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/f3ee1078d7099276195aed0603e12d26dfae1807
Updated•7 years ago
|
status-firefox51:
--- → unaffected
status-firefox52:
--- → unaffected
status-firefox53:
--- → unaffected
status-firefox54:
--- → affected
status-firefox-esr45:
--- → unaffected
status-firefox-esr52:
--- → unaffected
Comment 5•7 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/f3ee1078d709
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla54
Updated•7 years ago
|
Comment 6•7 years ago
|
||
Comment on attachment 8842096 [details] [diff] [review] Capture a strong reference to nsRootPresContext in EnsureEventualDidPaintEvent This needs to be uplifted if bug 1302071 gets approved.
Attachment #8842096 -
Flags: approval-mozilla-aurora?
Comment on attachment 8842096 [details] [diff] [review] Capture a strong reference to nsRootPresContext in EnsureEventualDidPaintEvent Not taking the uplift from bug 1302071 so we shouldn't need this on 53 aurora. (It's only aurora for a couple more days)
Attachment #8842096 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora-
Updated•7 years ago
|
Group: layout-core-security → core-security-release
Updated•7 years ago
|
Flags: qe-verify-
Whiteboard: [post-critsmash-triage]
Updated•7 years ago
|
Whiteboard: [post-critsmash-triage] → [post-critsmash-triage][adv-main54+]
Updated•6 years ago
|
Group: core-security-release
You need to log in
before you can comment on or make changes to this bug.
Description
•