OSV-2022-637 Segv on unknown address in mrb_bint_cmp
Not scored
Published
Check this codebase for OSV-2022-637 and fix it if it is affected.
What it is: OSV-2022-637 is a vulnerability in mruby, published on 27 Jul 2022.
Exploitation: There is no known exploitation of OSV-2022-637 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-2022-637/ (Markdown: https://insights.sbomify.com/OSV-2022-637/index.md)
A null pointer dereference in the mrb_bint_cmp function can cause a segmentation fault, leading to denial of service in applications using the library.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Not stated
- Victim action needed
- Not needed
- Fix
- None listed
What is OSV-2022-637?
OSV-2022-637 is a vulnerability in mruby, published on 27 Jul 2022.
Official description
OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=49493
Crash type: Segv on unknown address
Crash state:
mrb_bint_cmp
cmpnum
num_cmp
Which versions are affected by OSV-2022-637?
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-2022-637?
No fix has been published for OSV-2022-637 yet. Limit exposure of the affected software until one is available.
Is OSV-2022-637 being exploited?
There is no known exploitation of OSV-2022-637 in the wild and no public exploit code.