Application crash via unguarded slice bounds
Published Jan 5, 2021 · Updated Aug 4, 2024
Denial of service in tidwall GJSON 1.6.5 and earlier allows remote attackers to crash applications that parse crafted JSON input. The unwrap function evaluates an object-marker check outside its length guard, then slices a one-byte value using invalid bounds and triggers a runtime panic. Exposure requires a consuming application to pass attacker-controlled JSON or paths to an affected GJSON API; the library itself provides no network service.
Summary
What happened
Denial of service in tidwall GJSON 1.6.5 and earlier allows remote attackers to crash applications that parse crafted JSON input. The unwrap function evaluates an object-marker check outside its length guard, then slices a one-byte value using invalid bounds and triggers a runtime panic. Exposure requires a consuming application to pass attacker-controlled JSON or paths to an affected GJSON API; the library itself provides no network service.
The record
- CVE
- CVE-2020-36067
- Published
- Jan 5, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-129, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 5, 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
- GJSON slice-bounds panic reproducerproof 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