Search the Community
Showing results for tags 'jsc'.
-
JSC suffers from a data mishandling bug in ytecodeGenerator::emitEqualityOpImpl. View the full article
-
- jsc
- bytecodegenerator::emitequalityopimpl
-
(and 2 more)
Tagged with:
-
The doesGC function simply takes a node, and tells if it might cause a garbage collection. This function is used to determine whether to insert write barriers. But it is missing some cases such as StringCharAt, StringCharCodeAt and GetByVal that might cause a garbage collection via rope strings. As a result, it can lead to a use-after-free condition. View the full article
-
Exploits WebKit JSC AbstractValue::set Use-After-Free
1337day-Exploits posted a topic in Updated Exploits
WebKit JSC suffers from a use-after-free vulnerability that can be used to bypass write barriers. View the full article -
When a for-in loop is executed, a JSPropertyNameEnumerator object is created at the beginning and used to store the information of the input object to the for-in loop. Inside the loop, the structure ID of the "this" object of every get_by_id expression taking the loop variable as the index is compared to the cached structure ID from the JSPropertyNameEnumerator object. If it's the same, the "this" object of the get_by_id expression will be considered having the same structure as the input object to the for-in loop has. The problem is, it doesn't have anything to prevent the structure from which the cached structure ID from being freed. As structure IDs can be reused after their owners get freed, this can lead to type confusion. View the full article