# CVE-2022-32507: Missing authorization in n/a

> Unprivileged users can execute privileged BLE commands on Nuki Smart Locks due to missing access controls, allowing unauthorized device manipulation.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-jrvv-3x7m-vqjc

## What is CVE-2022-32507?

CVE-2022-32507 is a high-severity missing authorization vulnerability in n/a, published on 9 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered on certain Nuki Home Solutions devices. Some BLE commands, which should have been designed to be only called from privileged accounts, could also be called from unprivileged accounts. This demonstrates that no access controls were implemented for the different BLE commands across the different accounts. This affects Nuki Smart Lock 3.0 before 3.3.5 and Nuki Smart Lock 2.0 before 2.12.4.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2022-32507 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-32507 is a high-severity missing authorization vulnerability in n/a, published on 9 May 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-32507 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-32507/ (Markdown: https://insights.sbomify.com/CVE-2022-32507/index.md)
```

## Sources

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

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