Interpreter crash via null url_encode argument
Published Apr 4, 2023 · Updated Feb 14, 2025
NULL pointer dereference in Jsish 3.0.11 and earlier allows remote attackers to crash the interpreter through a crafted script. The encodeURI path passes a null string into url_encode, which forwards it to Jsi_Strlen and ultimately strlen without a null check. The application must evaluate attacker-supplied JavaScript; the demonstrated consequence is an interpreter segmentation fault.
Summary
What happened
NULL pointer dereference in Jsish 3.0.11 and earlier allows remote attackers to crash the interpreter through a crafted script. The encodeURI path passes a null string into url_encode, which forwards it to Jsi_Strlen and ultimately strlen without a null check. The application must evaluate attacker-supplied JavaScript; the demonstrated consequence is an interpreter segmentation fault.
The record
- CVE
- CVE-2020-23259
- Published
- Apr 4, 2023
- Updated
- Feb 14, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 4, 2023CVE publishedPublication date reported by the CVE source.
- Feb 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Jsish encodeURI null-pointer proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo