#javascriptCore

Vulnerability weaponization is the most frequently discussed topic of the #exploit development lifecycle. Here's our take on weaponizing a #JavaScriptCore vulnerability from the ground up: #Pwn2Own part four

It's kind of cool to read the #JavaScriptCore tests just for the #exotic #JavaScript

Been exploring WebKit/JSC exploitation and wrote up a step-by-step walkthrough - from a caged OOB bug to cage-free arbitrary R/W with diagrams + a lab you can build. #WebKit #JavaScriptCore #BrowserExploitation #exploitdev #pwn

One of our favorite #debugging technologies comes from @mozilla, so this week we wanted to help highlight an amazing project. Part three of our #Pwn2Own series makes use of timeless debugging to root cause an exploitable race condition in #JavaScriptCore:

REMIND/TONITE (1900 CET ONLINE @ #Zoom), @ctietze: "Make your app extensible with #JavaScriptCore"!

New write-up with @GenericCoding on pois0nSword, our iOS 26.1 port of DarkSword: bypassing PAC to reach arbitrary native calls from a WebKit renderer R/W, by making dyld's own loader do the write. #WebKit #JavaScriptCore #iOS #exploitdev

🚀"Bun speeds things up by utilizing the JavaScriptCore engine, while Node.js relies on the JavaScript V8 engine. JavaScriptCore is optimized for quicker startup, making Bun a great choice for faster performance. 💨 #NodeJS #JavaScriptCore #Bun #100daysofcoding"

WebAssembly: Wasmer 3.3 bringt Unterstützung von JavaScriptCore #Backend #JavaScriptCore

Interesting article - Is Bun.js the Node.js killer? #v8 #JavaScriptCore #bun #nodeJS #JavaScript #webdevelopment #webdev

🛠 WebKitGTK+ development release 2.21.1 is now available! 👉 We are moving to a new, GLib-based API for JavaScriptCore and deprecating most of the DOM bindings API. Developers, please test and let us know what you think! 📜 Release notes:

The new JSC API in 2.21.x should make it much more convenient to interact with the JavaScript world from your C/C++ code — or from any other languages supported through GObject-Introspection 🙌. Lack of introspection support was one of the shortcomings of the old API.

The documentation for the new GLib-based #JavaScriptCore API we are introducing in the 2.21.x development releases is now available in our website, and should be fully GObject-Introspectable: 🛠

live keynote on #javascriptcore from @filpizlo at #MPLR21

#JavaScriptCore CVE-2019-8765 GetterSetter Type Confusion #0day #Zeroday #Exploit #Exploits #Security

Don’t we all like to have the flexibility to follow any pattern for naming exported Swift API without limiting us to predefined conventions? Luckily, there is a different way of doing it: #functions #JavaScriptCore #JSExportAs #selectors #Swift #ios

What if @Nodejs used @mozilla's @SpiderMonkeyJS instead of Chrome's @v8js? 🤯🔥 🧵/1 #javascript #bun #deno #nodejs #jsruntime #tutorial #codechallenge #100daysofcode #diy #advancedjs #gitpod

One of the best videos I've ever recorded is the one I teach how to recreate Node.js from Scratch and it has reached more than 100K people around the globe🥳 I have researched a lot about the main components used in the original project such as Event Loop, V8, and C++ layers /2

If we compare @Nodejs with other competitors such as #Bun and @deno_land we can see a lot of similarities and good practices Whereas Node.js and Deno use V8 Bun uses #JavaScriptCore to execute JavaScript code Well... this raises questions. /3

Our next event (2022-11-24, 1900 CET ONLINE (#Zoom), @ctietze: "Make your app extensible with #JavaScriptCore"!

Been testing @panic's upcoming Nova code editor for a while. It has the snappiness of @sublimehq, the thoughtful details of @macromates's #textmate. The power of #JavaScriptCore, and the flexibility of @Microsoft's Language Server Protocol should bring it close to @code.

The first is always special - My first task as an Igalian and WebKit contributor was to refactor register information in the JSC backend. Happy to say the bird has landed: #igalia #webkit #javascriptcore

The #NativeScript team is working on total revamp of the #iOS runtime. The goal is to use the V8 engine instead of #JavaScriptCore. Several months ago the team shipped an alpha version of this runtime and now it’s time to announce the next iteration.

#phrack "Attacking JavaScript Engines: A case study of #JavaScriptCore and #CVE-2016-4622" by @5aelo

Do you know those tasks where you think : "Sure - it will take a couple of weeks.". Month and half later: "What da' hell?" Well, for...of optimization with intrinsics just landed in JSC for 32 bit archs: #igalia #javascriptcore #webkit