dbcve.org
RubyApplication · Ruby Lang

CVE-2022-28739

HIGH · 7.5 CVSS v3.1 Published 2022-05-09
Fix available
A fix is available. Upgrade to 2.6.10 / 2.7.6 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
There is a buffer over-read in Ruby before 2.6.10, 2.7.x before 2.7.6, 3.x before 3.0.4, and 3.1.x before 3.1.2. It occurs in String-to-Float conversion, including Kernel#Float and String#to_f.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A buffer over-read vulnerability in Ruby's String-to-Float conversion functions (Kernel#Float and String#to_f) allows reading memory beyond the intended buffer boundary, potentially leading to information disclosure or denial of service. The vulnerability exists in Ruby versions before 2.6.10, 2.7.x before 2.7.6, 3.x before 3.0.4, and 3.1.x before 3.1.2.

MitigationUpgrade Ruby to version 2.6.10, 2.7.6, 3.0.4, or 3.1.2 or later to patch the buffer over-read vulnerability in String-to-Float conversion.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RubyApplication
Affected:< 2.6.10>= 2.7.0, < 2.7.6>= 3.0.0, < 3.0.4>= 3.1.0, < 3.1.2
Debian LinuxOperating system
Affected:= 9.0= 10.0= 11.0
macOSOperating system
Affected:>= 11.0, < 11.7.1>= 12.0, < 12.6.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Ruby version
    Run 'ruby --version' in the terminal to see the installed Ruby version
    Affected if The version displayed is less than 2.6.10, between 2.7.0-2.7.5, between 3.0.0-3.0.3, or between 3.1.0-3.1.1
  2. Identify all Ruby installations on the system
    Run 'which -a ruby' to find all Ruby binaries in PATH, then check each version with 'ruby --version'
    Affected if Any discovered Ruby installation falls within the affected version ranges
  3. Check for Bundler or project-specific Ruby versions
    If using Bundler, run 'bundle exec ruby --version' within the project directory; for rbenv/rvm/asdf, run 'rbenv versions', 'rvm list', or 'asdf list ruby'
    Affected if Any project-specific or managed Ruby version is in the affected ranges
  4. Verify the vulnerable functions can be called
    Run 'ruby -e "puts Float("1.0"); puts "1.0".to_f' to confirm String-to-Float conversion functions are available
    Affected if The functions execute without error, confirming the vulnerable code path exists

The environment is affected if any installed Ruby version matches the vulnerable ranges: < 2.6.10, >= 2.7.0 and < 2.7.6, >= 3.0.0 and < 3.0.4, or >= 3.1.0 and < 3.1.2.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.6.10 / 2.7.6 / 3.0.4 or later
Fixed in 2.6.102.7.63.0.4
Interim mitigation

Upgrade Ruby to version 2.6.10, 2.7.6, 3.0.4, or 3.1.2 or later to patch the buffer over-read vulnerability in String-to-Float conversion.

Recommended fix High confidence

Ruby 2.6.10, 2.7.6, 3.0.4, or 3.1.2 (depending on your release branch)

  1. Check current Ruby version by running `ruby --version`
  2. Identify which Ruby release branch you are using (2.6.x, 2.7.x, 3.0.x, or 3.1.x)
  3. If using Ruby 2.6.x: upgrade to Ruby 2.6.10
  4. If using Ruby 2.7.x: upgrade to Ruby 2.7.6
  5. If using Ruby 3.0.x: upgrade to Ruby 3.0.4
  6. If using Ruby 3.1.x: upgrade to Ruby 3.1.2
  7. Verify the upgrade was successful by running `ruby --version` and confirm the version number matches a fixed release
Caveat Ruby minor version upgrades typically have backward compatibility, but test your application after upgrading to ensure no regressions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ruby Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-28739 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-28739 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data