# CVE-2022-40363: Memory corruption in n/a

> Attackers can cause a Denial of Service on Flipper Zero devices by loading a crafted NFC file due to a buffer overflow.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 Sep 2022
- **Updated:** 21 May 2025
- **Also known as:** GHSA-33v4-4p2r-hcrr

## What is CVE-2022-40363?

CVE-2022-40363 is a medium-severity memory corruption vulnerability in n/a, published on 29 Sep 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A buffer overflow in the component nfc_device_load_mifare_ul_data of Flipper Devices Inc., Flipper Zero before v0.65.2 allows attackers to cause a Denial of Service (DoS) via a crafted NFC file.

Weakness: CWE-787 (Out-of-bounds Write)

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

It affects 1 product.


Products: Flipperzero Flipper Zero Firmware.

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

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

## Is CVE-2022-40363 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-40363 exists.

Public exploit code:

- A buffer overflow in the component nfc_device_load_mifare_ul_data of Flipper Devices Inc., Flipper Zero before v0.65.2 allows attackers to cause a Denial of Service (DoS) via a crafted NFC file. CVE project by @Sn0wAlice (github_poc): https://github.com/Olafdaf/CVE-2022-40363

## Fix prompt for AI coding agents

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

What it is: CVE-2022-40363 is a medium-severity memory corruption vulnerability in n/a, published on 29 Sep 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-40363 exists.

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

## Sources

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

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