| Titre | Duktape https://github.com/svaarala/duktape <=2.99.99 Memory Corruption |
|---|
| Description | 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. |
|---|
| La source | ⚠️ https://github.com/hmKunlun/compileOOB/blob/main/api_bytecode.md |
|---|
| Utilisateur | kunlun (UID 95866) |
|---|
| Soumission | 20/05/2026 06:20 (il y a 4 mois) |
|---|
| Modérer | 14/06/2026 15:43 (25 days later) |
|---|
| Statut | Accepté |
|---|
| Entrée VulDB | 370859 [svaarala duktape jusqu’à 2.99.99 duk_api_bytecode.c count_instr buffer overflow] |
|---|
| Points | 20 |
|---|