-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ReportFatalException2 #6625
Comments
Can you tell me, where did you find this code, you wrote it by yourself? |
I try to find some security bugs by fuzzing.
…---Original---
From: ***@***.***>
Date: Tue, Mar 16, 2021 18:40 PM
To: ***@***.***>;
Cc: ***@***.******@***.***>;
Subject: Re: [chakra-core/ChakraCore] ReportFatalException2 (#6625)
Can you tell me, where did you find this code, you wrote it by yourself?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@rain6851 thank you for all the submissions, though your email client is mangling your responses. Are you sure this is not a legitimate out-of-memory issue? Are you using an opensource fuzzer? We have been looking for a fuzzer to use on regular basis. |
It is a legitimate out-of-memory issue(The memory of my computer is over 32 G). I develop a new fuzzer by myself. |
Sorry, I am a bit confused - do you think this test should run out of memory?
|
I use htop to monitor memory usage. When testing the poc, I found that only a small amount of memory was used, and the program quit after reporting an error. |
OK, I see what is going on - CC @rhuanjl |
I suppose we could introduce a non-fatal "length is too big" error for cases with no actual memory pressure. |
This is a fuzzer output - fuzzers generate random combinations of code to try and hit obscure bugs. That said this specific case is a by design "feature" but I'm not sure if it's the right decision. Attempting to create a string or array with length >=2^32 Chakracore aborts - the other major JS engines throw a range error which I think we could do. @rain6851 thank you for the submission. |
There is a length out-of-bound error, I'll try to repurpose that here. This isn't really a bug in itself, somebody intended this kind of situations to throw OOM (there are even tests checking for the error). However I think we should not throw it "proactively" like this, but reserve it for situations when runtime actually runs out of memory. |
Use a more appropriate error for out of bounds length in JavascriptString::SetLength(). Closes chakra-core#6625 Closes chakra-core#6632 Closes chakra-core#6634
enviroment
ubuntu18
poc
callstack
The text was updated successfully, but these errors were encountered: