| عنوان | Duktape https://github.com/svaarala/duktape <=2.99.99 Memory Corruption |
|---|
| الوصف | Duktape's bytecode loader (`duk_api_bytecode.c`) uses the `DUK_ASSERT` macro for bounds checking. In Release builds, `DUK_ASSERT` is defined as a no-op, so the bounds check is completely removed. By crafting bytecode with an inflated `count_instr` field and a truncated buffer ending at the instruction data boundary, the loader reads 4 bytes past the heap allocation, which are then interpreted as bytecode instructions. |
|---|
| المصدر | ⚠️ https://github.com/hmKunlun/compileOOB/blob/main/api_bytecode.md |
|---|
| المستخدم | kunlun (UID 95866) |
|---|
| ارسال | 20/05/2026 06:20 AM (2 أشهر منذ) |
|---|
| الاعتدال | 14/06/2026 03:43 PM (25 days later) |
|---|
| الحالة | تمت الموافقة |
|---|
| إدخال VulDB | 370859 [svaarala duktape حتى 2.99.99 duk_api_bytecode.c count_instr تلف الذاكرة] |
|---|
| النقاط | 20 |
|---|