# CVE-2023-50124: Hardcoded credentials in n/a

> An attacker can unlock the smart door lock by exploiting default credentials on a debug interface to replace stored fingerprints.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/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:** 11 Jan 2024
- **Updated:** 3 Sep 2024
- **Also known as:** GHSA-frwh-x637-x626

## What is CVE-2023-50124?

CVE-2023-50124 is a medium-severity vulnerability in n/a, published on 11 Jan 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Flient Smart Door Lock v1.0 is vulnerable to Use of Default Credentials. Due to default credentials on a debug interface, in combination with certain design choices, an attacker can unlock the Flient Smart Door Lock by replacing the fingerprint that is stored on the scanner.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Flient Smart Lock Advanced Firmware.

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

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

## Is CVE-2023-50124 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-50129](https://insights.sbomify.com/CVE-2023-50129/): Weak cryptography in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-50124 is a medium-severity vulnerability in n/a, published on 11 Jan 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-2023-50124 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-2023-50124/ (Markdown: https://insights.sbomify.com/CVE-2023-50124/index.md)
```

## Sources

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

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