# CVE-2023-25946: Auth bypass in Qrio Lock (Q-SL2)

> A network-adjacent attacker can bypass authentication to perform arbitrary operations on the Qrio Lock smart lock.

- **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:** 23 May 2023
- **Updated:** 31 Jan 2025
- **Also known as:** GHSA-x7p9-qfhh-r6x9

## What is CVE-2023-25946?

CVE-2023-25946 is a high-severity authentication bypass vulnerability in Qrio, inc. Qrio Lock (Q-SL2), published on 23 May 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Authentication bypass vulnerability in Qrio Lock (Q-SL2) firmware version 2.0.9 and earlier allows a network-adjacent attacker to analyze the product's communication data and conduct an arbitrary operation under certain conditions.

Weakness: CWE-287 (Improper Authentication), CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2023-25946?

It affects 1 product.


Products: Qrio Q-Sl2 Firmware.

## How do I fix CVE-2023-25946?

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

## Is CVE-2023-25946 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-25946 and fix it if it is affected.

What it is: CVE-2023-25946 is a high-severity authentication bypass vulnerability in Qrio, inc. Qrio Lock (Q-SL2), published on 23 May 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-2023-25946 in the wild and no public exploit code.

Affected product: Qrio, inc. Qrio Lock (Q-SL2). 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-2023-25946/ (Markdown: https://insights.sbomify.com/CVE-2023-25946/index.md)
```

## Sources

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

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