CVE-2020-10675: Infinite Loop in jsonparser

github.com/buger/jsonparser Updated 02 Oct 2025

Summary

14/04/2021
Yes i
High
7.5

CVE-2020-10675: Infinite loop in github.com/buger/jsonparser. Affects github.com/buger/jsonparser versions < 1.0.0. Fixed in 1.0.0. How to fix ↓

Also tracked for

The same CVE-2020-10675 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package under scrutiny is 'github.com/buger/jsonparser', which is a Go library for parsing JSON data. It provides a set of functions to extract values from JSON documents. This vulnerability affects versions prior to 1.0.0. The library allows attackers to cause a denial of service (infinite loop) through a Delete call.

Vulnerability Detail

The vulnerability (CVE-2020-10675) in 'github.com/buger/jsonparser' allows attackers to exploit an infinite loop in the Library API. By making a Delete call, an attacker can trigger the infinite loop, leading to a denial of service. This vulnerability has a CVSS score of 7.5, indicating a high severity level. The impact of this vulnerability can disrupt the availability of the affected application or system.

How To Fix

Latest published version: v1.6.1 as of 22 Oct 2026

go get github.com/buger/jsonparser@v1.6.1

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.0.0

This is the first release that contains the fix.

go get github.com/buger/jsonparser@v1.0.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. The recommended approach is to update the package to the fixed version.

Conclusion

The 'github.com/buger/jsonparser' package is vulnerable to an infinite loop issue, which can be exploited to cause a denial of service. To mitigate this vulnerability, it is crucial to update the package to version 1.0.0 or later. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for github.com/buger/jsonparser →

Share this vulnerability

FAQ

The impact of this vulnerability is a denial of service, potentially disrupting the availability of the affected application or system.

You can use Vulert's playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. It analyzes your Gopkg.lock file and provides real-time alerts for open-source vulnerabilities.

The CVSS score of this vulnerability is 7.5, indicating a high severity level.

Yes, a fix is available for this vulnerability. It is recommended to update the 'github.com/buger/jsonparser' package to version 1.0.0 or later.

There are no specific workarounds mentioned for this vulnerability. The recommended approach is to update the package to the fixed version.

Related vulnerabilities

Recent vulnerabilities recorded for github.com/buger/jsonparser.

How To Fix

Latest published version: v1.6.1 as of 22 Oct 2026

go get github.com/buger/jsonparser@v1.6.1

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

1.0.0

This is the first release that contains the fix.

go get github.com/buger/jsonparser@v1.0.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback