LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32823: Potential Denial-of-Service in bindata

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.

LowCVSS 3.7Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

This is a low-severity availability issue in the Ruby bindata gem. Older versions can spend excessive CPU time creating certain generated Bit or Integer classes. The realistic business impact is degraded service performance or partial denial of service, mainly where an application lets user input influence Ruby constant lookup.

Executive priority

Treat this as routine dependency hygiene unless the vulnerable pattern is exposed on public request paths. It should be fixed in normal patch cycles, faster for internet-facing Ruby services where untrusted input can influence class resolution.

Technical view

bindata versions before 2.4.10 have slow creation behavior for some BinData classes, such as very large Bit<N> constants. The CVE describes risk when this is combined with user-controlled constantize behavior. Version 2.4.10 improved Bit and Integer creation time. The CVSS score is 3.7 with low availability impact only.

Likely exposure

Exposure is most likely in Ruby applications using bindata below 2.4.10 and code paths where user-controlled input can be resolved through constantize. Applications that only use fixed, developer-defined BinData classes appear less likely to be practically exposed based on the provided sources.

Exploitation context

The source bundle does not show active exploitation, and the CVE is not listed as KEV. Exploitation appears application-dependent and high-complexity because it requires a vulnerable bindata version plus a reachable user-controlled constantize pattern that can trigger expensive class creation.

Researcher notes

The central condition is not merely using bindata; it is combining pre-2.4.10 bindata with unsafe constant resolution from user input. Evidence provided identifies CPU-based DoS potential and the 2.4.10 performance improvement, but does not provide exploit-in-the-wild confirmation.

Mitigation direction

  • Upgrade bindata to version 2.4.10 or later.
  • Avoid resolving user input with constantize in bindata-related paths.
  • Review vendor guidance for applications bundling bindata.
  • Prioritize production Ruby services with external request paths.

Validation and detection

  • Check Gemfile.lock or dependency inventory for bindata below 2.4.10.
  • Search code for user-controlled constantize or similar constant resolution.
  • Confirm production deployments use the updated dependency version.
  • Review request paths that parse untrusted input with bindata.
Prepared
Confidence
high
Sources
7

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-400: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-32823 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
6Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3.7CVSS 3.1LowCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L2.21.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.7Low
CVSS 3.1 vector shape for CVE-2021-32823Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
dmendelbindata< 2.4.10Listed
Weakness

CWE details

CWE-400

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.