# CVE-2022-23884: Integer overflow in n/a

> An integer overflow in the packet deserializer allows attackers to bypass bounds checks, potentially leading to code execution or server crashes.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-wvm2-72hm-jh6v

## What is CVE-2022-23884?

CVE-2022-23884 is a critical vulnerability in n/a, published on 28 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mojang Bedrock Dedicated Server 1.18.2 is affected by an integer overflow leading to a bound check bypass caused by PurchaseReceiptPacket::_read (packet deserializer).

Weakness: CWE-190 (Integer Overflow or Wraparound)

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

It affects 1 product.


Products: Minecraft Bedrock Server.

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

No fix has been published for CVE-2022-23884 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-23884 being exploited?

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

Public exploit code:

- Details,PoC and patches for CVE-2022-23884 (github_poc): https://github.com/nanaao/CVE-2022-23884

## Fix prompt for AI coding agents

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

What it is: CVE-2022-23884 is a critical vulnerability in n/a, published on 28 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-23884 in the wild and no public exploit code.

Affected product: n/a. 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-23884/ (Markdown: https://insights.sbomify.com/CVE-2022-23884/index.md)
```

## Sources

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

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