svaarala duktape duk_api_bytecode.c memory corruption
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: partial
Summary
A weakness has been identified in svaarala duktape up to 2.99.99. This issue affects some unknown processing of the file duk_api_bytecode.c. Executing a manipulation of the argument count_instr can lead to memory corruption. The attack requires local access. The exploit has been made available to the public and could be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- svaarala duktape
2.99.0, 2.99.1, 2.99.2, 2.99.3, 2.99.4, 2.99.5, 2.99.6, 2.99.7, 2.99.8, 2.99.9, 2.99.10, 2.99.11, 2.99.12, 2.99.13, 2.99.14, 2.99.15, 2.99.16, 2.99.17, 2.99.18, 2.99.19, 2.99.20, 2.99.21, 2.99.22, 2.99.23, 2.99.24, 2.99.25, 2.99.26, 2.99.27, 2.99.28, 2.99.29, and 70 more