Remote code execution via unchecked precision value
Published Jul 13, 2021 · Updated Aug 4, 2024
Stack buffer overflow in jsish before 3.0.7 allows remote attackers to execute arbitrary code through a crafted toPrecision argument. NumberToPrecisionCmd accepts an integer precision with no upper bound and passes it to snprintf for a 100-byte stack buffer, allowing oversized output to overwrite the stack. Exploitation requires an unauthenticated network path that causes jsish to evaluate attacker-controlled JavaScript; the public proof of concept demonstrates a crash, while the CVE records arbitrary code execution.
Summary
What happened
Stack buffer overflow in jsish before 3.0.7 allows remote attackers to execute arbitrary code through a crafted toPrecision argument. NumberToPrecisionCmd accepts an integer precision with no upper bound and passes it to snprintf for a 100-byte stack buffer, allowing oversized output to overwrite the stack. Exploitation requires an unauthenticated network path that causes jsish to evaluate attacker-controlled JavaScript; the public proof of concept demonstrates a crash, while the CVE records arbitrary code execution.
The record
- CVE
- CVE-2020-22873
- Published
- Jul 13, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-120
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 13, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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.
Weakness, pattern, technique
Public exploit references
- jsish toPrecision stack-overflow 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