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

> Attackers can bypass biometric authentication in Devolutions Password Hub for iOS by rapidly failing attempts, gaining unauthorized access to stored credentials.

- **Severity:** Medium 6.6 (`CVSS:3.1/AV:P/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qxhp-mp7h-vg86

## What is CVE-2022-23849?

CVE-2022-23849 is a medium-severity authentication bypass vulnerability in n/a, published on 3 Mar 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The biometric lock in Devolutions Password Hub for iOS before 2021.3.4 allows attackers to access the application because of authentication bypass. An attacker must rapidly make failed biometric authentication attempts.

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

It affects 1 product.


Products: Devolutions Password Hub.

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

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

## Is CVE-2022-23849 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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