A type confusion in jsish 2.0 allows incorrect control flow during execution of the OP_NEXT opcode. When an “instanceof” expression uses an array element access as the left-hand operand inside a for-in loop, the instructions implementation leaves an additional array reference on the stack rather than consuming it during OP_INSTANCEOF. As a result, OP_NEXT interprets the array as an iterator object and reads the iterCmd function pointer from an invalid structure, potentially causing a crash or enabling code execution depending on heap layout.
References
| Link | Resource |
|---|---|
| https://blog.mcsky.ro/writeups/2025/11/15/inline8-writeup.html | Exploit Third Party Advisory |
| https://blog.mcsky.ro/writeups/2025/11/15/inline8-writeup.html | Exploit Third Party Advisory |
Configurations
History
No history.
Information
Published : 2025-12-29 15:16
Updated : 2025-12-31 20:04
NVD link : CVE-2025-65570
Mitre link : CVE-2025-65570
CVE.ORG link : CVE-2025-65570
JSON object : View
Products Affected
jsish
- jsish
CWE
CWE-843
Access of Resource Using Incompatible Type ('Type Confusion')
