Skip to content
Fencer Vulns
low 3.7

CVE-2021-32823 json

Potential Denial-of-Service in bindata

published 2021-06-23 5 y ago modified 2026-09-08 2 mo ago also BIT-gitlab-2021-32823 , EUVD-2021-1335 , GHSA-hj56-84jw-67h6

cvss
3.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.9%
EPSS 1.9% chance of exploitation in 30 days, percentile 79%
public exploits
0
none known

Summary

In the bindata RubyGem before version 2.4.10 there is a potential denial-of-service vulnerability. In affected versions it is very slow for certain classes in BinData to be created. For example BinData::Bit100000, BinData::Bit100001, BinData::Bit100002, BinData::Bit<N>. In combination with <user_input>.constantize there is a potential for a CPU-based DoS. In version 2.4.10 bindata improved the creation time of Bits and Integers.

Patch / fix

  • rubygems bindata 2.4.10
  • bitnami gitlab 13.10.5, 13.11.5, 13.12.2
  • bindata_project bindata 2.4.10
  • gitlab gitlab 13.10.5, 13.11.5, 13.12.2
  • ruby-bindata Debian 14, Debian 13, Debian 12 2.4.14-1

debian advisories DEBIAN-CVE-2021-32823

Exploit prediction

1.87% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/rubysec/ruby-advisory-db/issues/476 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
GitHub 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P
OSV 3.1 3.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
rubygems bindata
<2.4.10
2.4.10
bitnami gitlab
>=12.0.0, <13.10.5
>=13.11.0, <13.11.5
>=13.12.0, <13.12.2
13.10.5
13.11.5
13.12.2

Affected products

  • dmendel bindata

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption
Technology feeds

References

Sources

Fencer Vulns 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.