The default bug view has changed. See this FAQ.

Crash [@ @0x0 | nsSVGTextFrame::GetCanvasTM]

RESOLVED DUPLICATE of bug 704706

Status

()

Core
SVG
--
critical
RESOLVED DUPLICATE of bug 704706
5 years ago
5 years ago

People

(Reporter: decoder, Unassigned)

Tracking

(Blocks: 1 bug, {crash, regression, testcase})

Other Branch
All
Linux
crash, regression, testcase
Points:
---

Firefox Tracking Flags

(firefox9 unaffected, firefox10 unaffected, firefox11+ fixed, firefox12+ fixed, firefox-esr10 unaffected, status1.9.2 unaffected)

Details

(Whiteboard: [sg:dupe 704706], crash signature)

(Reporter)

Description

5 years ago
This bug was filed from the Socorro interface and is 
report bp-c700f28a-c89e-44f2-b00e-2264a2111219 .
============================================================= 

The following SVG crashes Firefox Nightly (Build ID 20111218031140):


<svg xmlns="http://www.w3.org/2000/svg">
  <filter id="f_calcMode_linear_to" x="0%" y="0%" width="100%" height="100%">
    <feComponentTransfer>
      <feFuncR type="table" tableValues="0 2 2 0"/><text id="b">Text B</text></feComponentTransfer>
  </filter>
  <filter id="f_calcMode_discrete" x="0%" y="0%" width="100%" height="100%">
    <feComponentTransfer>
    </feComponentTransfer>
  </filter>
</svg>


Assuming sg:critical per severity rating guide, but I'm wondering why executing NULL should be relevant in a remote situation (it is under Windows when conducting local attacks but remote processes usually don't have this address mapped).
If we can prove that it's always EITHER a valid address OR null then it wouldn't be vulnerable, but the fact that our object is unexpectedly gone may mean we can't prove that. This testcase may always result in null, but until we know the cause we don't know if a slightly different one could end up with a different result.
I do not see a crash in Firefox 9 or 10a2.
status-firefox10: --- → unaffected
status-firefox11: --- → affected
status-firefox12: --- → affected
status-firefox9: --- → unaffected
tracking-firefox11: --- → +
tracking-firefox12: --- → +
Keywords: regression, regressionwindow-wanted

Comment 3

5 years ago
Didn't bug 704706 fix this? Are we getting crashes from builds with that patch in? If not this is a duplicate of that.
(In reply to Robert Longson from comment #3)
> Didn't bug 704706 fix this? Are we getting crashes from builds with that
> patch in? If not this is a duplicate of that.

Possibly so, I was testing with Dec 19, 2011 Mac nightly which crashed, and Dec 22, 2011 Mac nightly didn't.

Comment 5

5 years ago
The code change in that bug is designed to cover this case so if we're not getting crashes post that landing then this is a duplicate.
And as per Jesse mentions in bug 704706 comment 0, it may indeed be a regression from the last few days prior to Nov 22, 2011, or possibly bug 696078.
Keywords: regressionwindow-wanted
Duping per comment 5.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 704706

Comment 8

5 years ago
(In reply to Gary Kwong [:gkw, :nth10sd] from comment #6)
> And as per Jesse mentions in bug 704706 comment 0, it may indeed be a
> regression from the last few days prior to Nov 22, 2011, or possibly bug
> 696078.

Jesse was spot on, bug 696078 was the cause.
status1.9.2: --- → unaffected
status-firefox11: affected → fixed
status-firefox12: affected → fixed
Whiteboard: [sg:critical] → [sg:dupe 704706]
status-firefox-esr10: --- → unaffected
Group: core-security
You need to log in before you can comment on or make changes to this bug.