Use-after-poison in str_new_frozen_buffer in Ruby

ruby Updated 02 Oct 2025

Summary

17/04/2023
HIGH
Yes i
High
Not published

OSV-2023-322: Use-after-poison in str_new_frozen_buffer. Affects ruby versions >= 19aa30d5d515cd602211d4708e709913d5a136e1, < 628e432739e1d2578d357420aa652a97eb8c2649. Fixed in 628e432739e1d2578d357420aa652a97eb8c2649. How to fix ↓

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

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Ruby is a dynamic, open-source programming language known for its simplicity and productivity. It is widely used for web development, scripting, and system administration tasks. The vulnerability in question affects the Ruby package and specifically the 'str_new_frozen_buffer' function.

Vulnerability Detail

The vulnerability, identified as OSV-2023-322, is a use-after-poison issue in the 'str_new_frozen_buffer' function of the Ruby package. This vulnerability allows an attacker to read 8 bytes of uninitialized memory, potentially leading to information disclosure or remote code execution. The issue was discovered through an OSS-Fuzz report and has been assigned a severity rating of HIGH.

How To Fix

Minimum fixed version

628e432739e1d2578d357420aa652a97eb8c2649

This is the first release that contains the fix.

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

Workaround

No specific workaround has been provided for this vulnerability.

Conclusion

In conclusion, the 'str_new_frozen_buffer' function in the Ruby package is vulnerable to a use-after-poison issue. It is recommended to update to a version of Ruby that includes the fix for this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for ruby →

Share this vulnerability

FAQ

This vulnerability could potentially allow an attacker to read uninitialized memory, which may lead to the disclosure of sensitive information or the execution of arbitrary code.

The vulnerability was discovered through an OSS-Fuzz report, which identified a use-after-poison issue in the 'str_new_frozen_buffer' function of the Ruby package.

This vulnerability has been assigned a severity rating of HIGH.

Yes, a fix has been implemented in commit '628e432739e1d2578d357420aa652a97eb8c2649' of the Ruby repository. Updating to a version that includes this commit will address the vulnerability.

No specific workarounds have been provided for this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for ruby.

How To Fix

Minimum fixed version

628e432739e1d2578d357420aa652a97eb8c2649

This is the first release that contains the fix.

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