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

> A stack buffer overflow in the JSON parser allows attackers to execute arbitrary code on Nuki Smart Lock and Bridge devices.

- **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:** 9 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-pcv6-8pf7-r5hc

## What is CVE-2022-32504?

CVE-2022-32504 is a critical memory corruption vulnerability in n/a, published on 9 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on certain Nuki Home Solutions devices. The code used to parse the JSON objects received from the WebSocket service provided by the device leads to a stack buffer overflow. An attacker would be able to exploit this to gain arbitrary code execution on a KeyTurner device. This affects Nuki Smart Lock 3.0 before 3.3.5 and 2.0 before 2.12.4, as well as Nuki Bridge v1 before 1.22.0 and v2 before 2.13.2.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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


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

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

## Is CVE-2022-32504 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-32504 is a critical memory corruption vulnerability in n/a, published on 9 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-32504 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-32504/ (Markdown: https://insights.sbomify.com/CVE-2022-32504/index.md)
```

## Sources

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

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