OSV-2023-200 Segv on unknown address in mrb_vm_find_method
Not scored
Published
Check this codebase for OSV-2023-200 and fix it if it is affected.
What it is: OSV-2023-200 is a vulnerability in mruby, published on 18 Mar 2023.
Exploitation: There is no known exploitation of OSV-2023-200 in the wild and no public exploit code.
Affected packages and fixed versions:
- mruby (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-200/ (Markdown: https://insights.sbomify.com/OSV-2023-200/index.md)
A null pointer dereference in the mruby VM allows attackers to cause a denial of service via crafted input.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2023-200?
OSV-2023-200 is a vulnerability in mruby, published on 18 Mar 2023.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=57135
Crash type: Segv on unknown address
Crash state:
mrb_vm_find_method
mrb_vm_exec
mrb_vm_run
Which versions are affected by OSV-2023-200?
1 open source package ship an affected version, including mruby.
| Package | Affected | Fixed in |
|---|---|---|
mruby OSS-Fuzz | All versions | None |
How do I fix OSV-2023-200?
No fix has been published for OSV-2023-200 yet. Limit exposure of the affected software until one is available.
Is OSV-2023-200 being exploited?
There is no known exploitation of OSV-2023-200 in the wild and no public exploit code.