Closed Bug 1032208 Opened 10 years ago Closed 10 years ago

Assertion failure: v.isObject(), at json.cpp:508 or Crash [@ GetObjectClass] or Crash [@ js::ObjectClassIs] with Symbol and JSON

Categories

(Core :: JavaScript Engine, defect)

x86
Linux
defect
Not set
critical

Tracking

()

VERIFIED FIXED
mozilla33
Tracking Status
firefox33 --- verified
firefox-esr24 --- unaffected
firefox-esr31 --- unaffected

People

(Reporter: decoder, Assigned: jorendorff)

References

Details

(4 keywords, Whiteboard: [jsbugmon:update,bisect][adv-main33+])

Crash Data

Attachments

(3 files)

The following testcase asserts on mozilla-central revision b6408c32a170 (run with --fuzzing-safe --ion-eager):


JSON.stringify(Symbol());
Opt-crash trace:


Program received signal SIGSEGV, Segmentation fault.
0x00000000007e1458 in GetObjectClass (obj=0x7ffff7e1d040) at js/src/jsfriendapi.h:600
600         return reinterpret_cast<const shadow::Object*>(obj)->type->clasp;
#0  0x00000000007e1458 in GetObjectClass (obj=0x7ffff7e1d040) at js/src/jsfriendapi.h:600
#1  IsProxy (obj=0x7ffff7e1d040) at js/src/jsproxy.h:362
#2  is<js::ProxyObject> (this=0x7ffff7e1d040) at js/src/vm/ProxyObject.h:118
#3  js::ObjectClassIs (obj=..., classValue=js::ESClass_Array, cx=0x161a6e0) at js/src/jsobjinlines.h:1016
#4  0x00000000007ca9ca in Str (cx=0x161a6e0, v=..., scx=0x7fffffffc5c0) at js/src/json.cpp:513
#5  0x00000000007cb083 in Str (cx=<optimized out>, v=..., scx=0x7fffffffc5c0) at js/src/json.cpp:491
#6  0x00000000007cbe45 in js_Stringify (cx=<optimized out>, vp=..., replacer_=<optimized out>, space_=..., sb=...) at js/src/json.cpp:685
#7  0x00000000007ccbdc in json_stringify (cx=<optimized out>, argc=<optimized out>, vp=0x7fffffffcfc8) at js/src/json.cpp:873
rax     0x0     0
=> 0x7e1458 <js::ObjectClassIs(JS::HandleObject, js::ESClassValue, JSContext*)+8>:      mov    (%rax),%rcx



Although the opt-crash trace here seems to show a crash at 0x0, I've found that the test changes it's crash address when being passed strings to Symbol. I also saw crash addresses 0x13, 0xf and 0x1d so I must assume that one can control/influence the crash address somehow using the arguments. S-s and sec-high because of that.
Crash Signature: [@ GetObjectClass] [@ js::ObjectClassIs]
Keywords: crash, sec-high
Whiteboard: [jsbugmon:update,bisect]
Similar/related assertion (as requested by jorendorff):

Assertion failure: v.isString() || v.isObject(), at vm/TypedArrayObject.cpp:916
Flags: needinfo?(jorendorff)
Assignee: nobody → jorendorff
Attachment #8448220 - Flags: review?(jdemooij)
Flags: needinfo?(jorendorff)
Attachment #8448220 - Flags: review?(jdemooij) → review+
Comment on attachment 8448221 [details] [diff] [review]
bug-1032208-part-2-typed-arrays-v1.patch

Review of attachment 8448221 [details] [diff] [review]:
-----------------------------------------------------------------

::: js/src/tests/ecma_6/Symbol/typed-arrays.js
@@ +1,2 @@
> +/* Any copyright is dedicated to the Public Domain.
> + * http://creativecommons.org/licenses/publicdomain/ */

Personally I prefer jit-tests, because we run them on TBPL with --ion-eager, --baseline-eager etc.

@@ +5,5 @@
> +
> +var tests = [
> +    {T: Int16Array, result: 0},
> +    {T: Uint8Array, result: 0},
> +    {T: Float32Array, result: NaN}

Nit: use Uint8ClampedArray instead of Uint8Array (or test both).
Attachment #8448221 - Flags: review?(jdemooij) → review+
https://hg.mozilla.org/mozilla-central/rev/f81a509fc014
https://hg.mozilla.org/mozilla-central/rev/03f72dc8cbb1
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: in-testsuite?
Resolution: --- → FIXED
Target Milestone: --- → mozilla33
Status: RESOLVED → VERIFIED
Crash Signature: [@ GetObjectClass] [@ js::ObjectClassIs] → [@ GetObjectClass] [@ js::ObjectClassIs]
JSBugMon: This bug has been automatically verified fixed.
Crash Signature: [@ GetObjectClass] [@ js::ObjectClassIs] → [@ GetObjectClass] [@ js::ObjectClassIs]
This didn't go through sec-approval before going in. How far back does this go?
Was ESR31 affected by this?
Flags: needinfo?(choller)
Whiteboard: [jsbugmon:update,bisect] → [jsbugmon:update,bisect][adv-main33+]
I don't think so since Symbol was a very recent addition at that time, so the bugs we filed were Nightly only.
Flags: needinfo?(choller)
Group: core-security → core-security-release
Group: core-security-release
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: