gjson vulnerabilities and fixes
Recent CVEs affecting gjson, with upgrade or downgrade steps. 4 tracked.
gjson has 4 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 4. Most recent: 2021-10-22. Highest priority: CVE-2021-42836 (score 57/100).
- CVE-2021-42836 HIGH 7.5 UPGRADE GJSON before 1.9.3 allows a ReDoS (regular expression denial of service) attack.
- CVE-2020-36067 HIGH 7.5 UPGRADE GJSON <=v1.6.5 allows attackers to cause a denial of service (panic: runtime error: slice bounds out of range)
- CVE-2020-36066 HIGH 7.5 UPGRADE GJSON <1.6.5 allows attackers to cause a denial of service (remote) via crafted JSON.
- CVE-2020-35380 HIGH 7.5 UPGRADE GJSON before 1.6.4 allows attackers to cause a denial of service via crafted JSON.
FAQ
How do I fix gjson vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is gjson being exploited right now?
None of the tracked gjson CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which gjson CVE should I patch first?
CVE-2021-42836 currently ranks highest (57/100): GJSON before 1.9.3 allows a ReDoS (regular expression denial of service) attack..