CVE-2022-0080 json
Heap-based Buffer Overflow in mruby/mruby
published 2022-01-02 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-15300
- cvss
- 8.2
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 76%
- public exploits
- 0
- none known
Summary
mruby is vulnerable to Heap-based Buffer Overflow
Patch / fix
- mruby mruby/mruby 3.1
- mruby Debian 14, Debian 13, Debian 12 3.0.0-3
debian advisories DEBIAN-CVE-2022-0080
- mruby openSUSE Tumbleweed 3.0.0-3.1
opensuse advisories openSUSE-SU-2024:11753-1
- mruby Alpine 3.24, Alpine 3.23, Alpine 3.22 +5 more 3.1.0-r0
alpine advisories ALPINE-CVE-2022-0080
Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 17 mo ago
Exploit prediction
1.63% chance of exploitation in the next 30 days, higher than 76% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/59a70392-4864-4ce3-8e35-6ac2111d1e2e referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 8.2 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N |
| CISA ADP | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N |
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| CNA | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- mruby mruby/mruby
Classification
- Weakness
-
- CWE-122 Heap-based Buffer Overflow
References
-
github.com
/mruby/mruby/commit/28ccc664e5dcd3f9d55173e9afde77c4705a9ab6
patch, third-party-advisory
-
huntr.dev
/bounties/59a70392-4864-4ce3-8e35-6ac2111d1e2e
exploit, issue-tracking, patch, third-party-advisory
Sources
- CVE List CVE-2022-0080
- NVD CVE-2022-0080
Fencer Vulns 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.