OSV-2023-322 Use-after-poison in str_new_frozen_buffer
Not scored
Published
Check this codebase for OSV-2023-322 and fix it if it is affected.
What it is: OSV-2023-322 is an use after free vulnerability in ruby, published on 17 Apr 2023.
Exploitation: There is no known exploitation of OSV-2023-322 in the wild and no public exploit code.
Affected packages and fixed versions:
- ruby (OSS-Fuzz): affected all versions; no fix listed
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/OSV-2023-322/ (Markdown: https://insights.sbomify.com/OSV-2023-322/index.md)
A use-after-poison vulnerability in Ruby's string handling allows attackers to potentially execute code or cause denial of service.
- Exploited in the wild
- Not known
- Login needed
- Not stated
- Attackable
- Not stated
- Victim action needed
- Not stated
- Fix
- None listed
What is OSV-2023-322?
OSV-2023-322 is an use after free vulnerability in ruby, published on 17 Apr 2023.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=58079
Crash type: Use-after-poison READ 8
Crash state:
str_new_frozen_buffer
fstr_update_callback
rb_st_update
Which versions are affected by OSV-2023-322?
1 open source package ship an affected version, including ruby.
| Package | Affected | Fixed in |
|---|---|---|
ruby OSS-Fuzz | All versions | None |
How do I fix OSV-2023-322?
No fix has been published for OSV-2023-322 yet. Limit exposure of the affected software until one is available.
Upgrade to the fixed version. These bugs are found with fuzzing and sanitisers and avoided by memory-safe languages. More about Use after free.
Is OSV-2023-322 being exploited?
There is no known exploitation of OSV-2023-322 in the wild and no public exploit code.