# CVE-2022-1201: NULL Pointer Dereference in mrb_vm_exec with super in mruby/mruby

> An attacker can cause a denial of service by triggering a null pointer dereference in the mruby interpreter via the super keyword.

- **Severity:** High 7.1 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Apr 2022
- **Updated:** 2 Aug 2024
- **Also known as:** AZL-41093, DEBIAN-CVE-2022-1201, GHSA-p2wj-9vfc-2xj7, UBUNTU-CVE-2022-1201

## What is CVE-2022-1201?

CVE-2022-1201 is a high-severity vulnerability in mruby/mruby, published on 2 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

NULL Pointer Dereference in mrb_vm_exec with super in GitHub repository mruby/mruby prior to 3.2. This vulnerability is capable of making the mruby interpreter crash, thus affecting the availability of the system.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2022-1201?

It affects 1 product.


Products: Mruby Mruby.

## How do I fix CVE-2022-1201?

Upgrade to a fixed version.

## Is CVE-2022-1201 being exploited?

There is no known exploitation of CVE-2022-1201 in the wild and no public exploit code.

## Other vulnerabilities in mruby/mruby

- [CVE-2020-6838](https://insights.sbomify.com/CVE-2020-6838/): Use after free in n/a (critical 9.8)
- [CVE-2020-6839](https://insights.sbomify.com/CVE-2020-6839/): Memory corruption in n/a (critical 9.8)
- [CVE-2020-6840](https://insights.sbomify.com/CVE-2020-6840/): Use after free in n/a (critical 9.8)
- [CVE-2018-10199](https://insights.sbomify.com/CVE-2018-10199/): Use after free in n/a (critical 9.8)
- [CVE-2022-1212](https://insights.sbomify.com/CVE-2022-1212/): Use-After-Free in str_escape in mruby/mruby in mruby/mruby (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1201 and fix it if it is affected.

What it is: CVE-2022-1201 is a high-severity vulnerability in mruby/mruby, published on 2 Apr 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1201 in the wild and no public exploit code.

Affected product: mruby/mruby. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2022-1201/ (Markdown: https://insights.sbomify.com/CVE-2022-1201/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-1201
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-1201
- OSV: https://osv.dev/vulnerability/CVE-2022-1201

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-1201/
Summaries are generated and may contain mistakes; the official description above is the record.