Search the Community

WebKit suffers from an HTMLFrameElementBase::isURLAllowed universal cross site scripting vulnerability. View the full article

WebKit suffers from a same-origin policy bypass vulnerability in FrameLoader::clear. View the full article

WebKit suffers from a universal cross site scripting vulnerability using cached pages. View the full article

WebKit suffers from a user-agent shadow root leak in WebCore::ReplacementFragment::ReplacementFragment. View the full article

WebKit suffers from a universal cross site scripting vulnerability in WebCore::command. View the full article

WebKit has an issue where URI and synchronous page loads are susceptible to a universal cross site scripting vulnerability. View the full article

Webkit JSC JIT suffers from an uninitialized variable access vulnerability in ArgumentsEliminationPhase::transform. View the full article

WebKit suffers from a universal cross site scripting vulnerability via XSLT and nested document replacements. View the full article

WebKit suffers from a universal cross site scripting vulnerability due to synchronous page loads. View the full article

This Metasploit module exploits a type confusion bug in the Javascript Proxy object in WebKit. The DFG JIT does not take into account that, through the use of a Proxy, it is possible to run arbitrary JS code during the execution of a CreateThis operation. This makes it possible to change the structure of e.g. an argument without causing a bailout, leading to a type confusion (CVE-2018-4233). The type confusion leads to the ability to allocate fake Javascript objects, as well as the ability to find the address in memory of a Javascript object. This allows us to construct a fake JSCell object that can be used to read and write arbitrary memory from Javascript. The module then uses a ROP chain to write the first stage shellcode into executable memory within the Safari process and kick off its execution. The first stage maps the second stage macho (containing CVE-2017-13861) into executable memory, and jumps to its entrypoint. The CVE-2017-13861 async_wake exploit leads to a kernel task port (TFP0) that can read and write arbitrary kernel memory. The processes credential and sandbox structure in the kernel is overwritten and the meterpreter payloads code signature hash is added to the kernels trust cache, allowing Safari to load and execute the (self-signed) meterpreter payload. View the full article

Sony PlayStation 4 (PS4) versions prior to 6.20 webkit code execution proof of concept exploit. View the full article

WebKit JSC has an issue where reifyStaticProperty needs to set the PropertyAttribute::CustomAccessor flag for CustomGetterSetter. View the full article

[Hidden Content]

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

WebKit JSC suffers from a use-after-free vulnerability that can be used to bypass write barriers. View the full article

WebKit JSC suffers from out-of-bounds read and write vulnerabilities in JSArray::shiftCountWithArrayStorage. View the full article

WebKit JIT int32/double arrays can have proxy objects in the prototype chains. View the full article

WebKit JSC has an issue where BytecodeGenerator::hoistSloppyModeFunctionIfNecessary does not invalidate the ForInContext object. View the full article

WebKit JIT has type confusion bugs in ByteCodeParser::handleIntrinsicCall. 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

WebKit suffers from a WebCore::InlineTextBox::paint out-of-bounds read vulnerability. View the full article

WebKit suffers from a WebCore::RenderMultiColumnSet::updateMinimumColumnHeight use-after-free vulnerability. View the full article

WebKit suffers from a WebCore::SVGTRefElement::updateReferencedText use-after-free vulnerability. View the full article

WebKit suffers from a WebCore::AXObjectCache::handleMenuItemSelected use-after-free vulnerability. View the full article

WebKit suffers from a WebCore::Node::ensureRareData use-after-free vulnerability. View the full article