Skip to content
Fencer Intel
high 7.5

CVE-2020-35381 json

Denial of Service in jsonparser

published 5y ago modified 4mo ago also GHSA-8vrw-m3j9-j27c , GO-2021-0057 , EUVD-2022-3245

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.3%
EPSS 2.3% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

jsonparser 1.0.0 allows attackers to cause a denial of service (panic: runtime error: slice bounds out of range) via a GET call.

Patch / fix

  • go github.com/buger/jsonparser 1.1.1
  • golang-github-buger-jsonparser Debian 14, Debian 13, Debian 12 1.1.1-1

debian advisories DEBIAN-CVE-2020-35381

Is CVE-2020-35381 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2020-35381 updated cvss 7.5

jsonparser: GET call can lead to a slice bounds out of range

  • Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/search-collector-rhel9, rhacm2/search-aggregator-rhel8
    affected: no fix available

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.31% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/buger/jsonparser/issues/219 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 7.8 AV:N/AC:L/Au:N/C:N/I:N/A:C
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/buger/jsonparser
<1.1.1
1.1.1

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.