# CVE-2022-46480: Auth bypass in n/a

> Attackers can sniff unlock codes via Bluetooth to bypass authentication and unlock the smart lock device.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **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:** 4 Dec 2023
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-8hjq-w7g3-vg4c

## What is CVE-2022-46480?

CVE-2022-46480 is a high-severity authentication bypass vulnerability in n/a, published on 4 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect Session Management and Credential Re-use in the Bluetooth LE stack of the Ultraloq UL3 2nd Gen Smart Lock Firmware 02.27.0012 allows an attacker to sniff the unlock code and unlock the device whilst within Bluetooth range.

Weakness: CWE-384 (Session Fixation), CWE-294 (Authentication Bypass by Capture-replay)

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

It affects 1 product.


Products: U-Tec Ultraloq Ul3 Bt Firmware.

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

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

## Is CVE-2022-46480 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-46480 is a high-severity authentication bypass vulnerability in n/a, published on 4 Dec 2023. 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-46480 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-46480/ (Markdown: https://insights.sbomify.com/CVE-2022-46480/index.md)
```

## Sources

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

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