Closed
Bug 595689
Opened 14 years ago
Closed 14 years ago
Malformed font leads to crash in Apple's ATSUI [@OTL::GCommon::GetLookups]
Categories
(Core :: Graphics, defect)
Tracking
()
VERIFIED
FIXED
People
(Reporter: posidron, Assigned: jfkthame)
References
(Blocks 1 open bug)
Details
(Keywords: verified1.9.2, Whiteboard: [sg:vector-critical? (Apple)])
Attachments
(1 file, 2 obsolete files)
(deleted),
text/plain
|
Details |
Table: b'GSUB'
Number of replaced values: 4
Offset: 102/0x000066 Value: ['ff', 'ff', 'ff', 'ff']
Offset: 389/0x000185 Value: ['40', '00']
Offset: 734/0x0002de Value: ['00', '00', '00', '01']
Offset: 749/0x0002ed Value: ['00', '00', '00', '00', '00', '00', '00', '01']
Execute the provided html file.
PS: I am not able to get a real callstack for this one. This bug was marked as a security issue because of uncertainty.
Reporter | ||
Comment 1•14 years ago
|
||
Reporter | ||
Comment 2•14 years ago
|
||
Attachment #474552 -
Attachment is obsolete: true
Reporter | ||
Comment 3•14 years ago
|
||
Attachment #474551 -
Attachment is obsolete: true
Updated•14 years ago
|
blocking2.0: --- → ?
Updated•14 years ago
|
Assignee: nobody → jdaggett
Comment 5•14 years ago
|
||
Per Joe these are likely exploitable on trunk with a slightly modified testcase, so marking that this applies to trunk as well.
Whiteboard: [sg:critical]
Version: 1.9.2 Branch → Trunk
Updated•14 years ago
|
Summary: Malformed font leads to crash [@OTL::GCommon::GetLookups] → Malformed font leads to crash in Apple's ATSUI [@OTL::GCommon::GetLookups]
Comment 6•14 years ago
|
||
CrashWrangler reports "is exploitable" with latest seed build (10.6.5 10H542).
Comment 7•14 years ago
|
||
Command line to run testcase:
MOZ_CRASHREPORTER_DISABLE=1 "/Applications/Firefox.app/Contents/MacOS/firefox-bin" "file:///Users/jd/Desktop/b595689/index.html"
Comment 8•14 years ago
|
||
Please callstack affecting Trunk, preferably with guardmalloc
Comment 9•14 years ago
|
||
Ran the test against trunk with harfbuzz disabled, no crash. So this appears to be 1.9.2 only (since we use ATSUI in 1.9.2 and CoreText on trunk when harfbuzz is disabled).
Version: Trunk → 1.9.2 Branch
Reporter | ||
Comment 10•14 years ago
|
||
John, gmalloc takes a bit longer here. In the meantime I have uploaded the new testcase against trunk. The testcase is based on your FakeIndic idea. I just removed the morx table and replaced the GSUB table.
Updated•14 years ago
|
blocking2.0: ? → final+
Comment 11•14 years ago
|
||
(In reply to comment #10)
> Created attachment 477470 [details]
> testcase-trunk
>
> John, gmalloc takes a bit longer here. In the meantime I have uploaded the new
> testcase against trunk. The testcase is based on your FakeIndic idea. I just
> removed the morx table and replaced the GSUB table.
Still not able to crash using testcase-trunk with trunk code with harfbuzz enabled or disabled.
Do I need to reload lots of times? If possible, please attach the callstack for a trunk crash.
Tested with:
Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b7pre) Gecko/20100928 Firefox/4.0b7pre
10.6.5 10H542
Reporter | ||
Comment 12•14 years ago
|
||
It's not reproducible against trunk on 10.6.5.
Assignee | ||
Comment 13•14 years ago
|
||
This will be fixed by the OTS sanitizer (bug 527276).
Depends on: CVE-2010-3768
Updated•14 years ago
|
Whiteboard: [sg:critical] → [sg:vector-critical? (Apple)]
Assignee | ||
Updated•14 years ago
|
Assignee: jdaggett → jfkthame
Status: NEW → RESOLVED
Closed: 14 years ago
status1.9.2:
--- → .13-fixed
Resolution: --- → FIXED
Comment 14•14 years ago
|
||
Verified fixed in 1.9.2.13 with Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6;
en-US; rv:1.9.2.13pre) Gecko/20101118 Namoroka/3.6.13pre using testcase. Test
no longer crashes as it does in 1.9.2.12.
Status: RESOLVED → VERIFIED
Keywords: verified1.9.2
Updated•13 years ago
|
Attachment #474557 -
Attachment is private: true
Updated•13 years ago
|
Attachment #477470 -
Attachment is private: true
Updated•13 years ago
|
Group: core-security
Reporter | ||
Updated•13 years ago
|
Blocks: fuzzing-fonts
You need to log in
before you can comment on or make changes to this bug.
Description
•