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.
Metrics
Affected Vendors & Products
References
History
Wed, 31 Dec 2025 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:jsish:jsish:2.0:*:*:*:*:*:*:* |
Wed, 31 Dec 2025 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-843 | |
| Metrics |
cvssV3_1
|
Mon, 29 Dec 2025 23:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Jsish
Jsish jsish |
|
| Vendors & Products |
Jsish
Jsish jsish |
Mon, 29 Dec 2025 15:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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 |
|
Status: PUBLISHED
Assigner: mitre
Published: 2025-12-29T00:00:00.000Z
Updated: 2025-12-31T16:59:28.908Z
Reserved: 2025-11-18T00:00:00.000Z
Link: CVE-2025-65570
Updated: 2025-12-31T16:41:34.333Z
Status : Analyzed
Published: 2025-12-29T15:16:01.763
Modified: 2025-12-31T20:04:10.750
Link: CVE-2025-65570
No data.