Skip to content
Fencer Intel
medium 5.5

CVE-2022-0890 json

NULL Pointer Dereference in mruby/mruby

published 4y ago modified 4mo ago also EUVD-2022-15926

cvss
5.5
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 57%
public exploits
0
none known

Summary

NULL Pointer Dereference in GitHub repository mruby/mruby prior to 3.2.

Patch / fix

  • mruby mruby/mruby 3.2
  • mruby Debian 14, Debian 13, Debian 12 3.1.0-1

debian advisories DEBIAN-CVE-2022-0890

  • mruby openSUSE Tumbleweed 3.1.0-1.1

opensuse advisories openSUSE-SU-2024:12703-1

  • mruby Alpine 3.24, Alpine 3.23, Alpine 3.22 +5 more 3.1.0-r0

alpine advisories ALPINE-CVE-2022-0890

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • rust Azure Linux 3.0 1.75.0-1

azure linux advisories AZL-41766

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2022-0890 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.83% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • huntr.dev https://huntr.dev/bounties/68e09ec1-6cc7-48b8-981d-30f478c70276 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.0 5.5 CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
NVD 2.0 7.1 AV:N/AC:M/Au:N/C:N/I:N/A:C

Affected products

  • mruby mruby/mruby

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.