# CVE-2023-24022: Hard Coded Credential Crypt Vulnerability

> Remote attackers can use hardcoded credentials to authenticate via SSH on Baicells LTE eNodeB devices, gaining unauthorized access.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jan 2023
- **Updated:** 2 Apr 2025
- **Also known as:** GHSA-hqr2-p4fq-45vv

## What is CVE-2023-24022?

CVE-2023-24022 is a critical vulnerability in Baicells Nova 227, published on 24 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Baicells Nova 227, Nova 233, and Nova 243 LTE TDD eNodeB devices with firmware through RTS/RTD 3.7.11.3 have hardcoded credentials that are easily discovered and can be used by remote attackers to authenticate via ssh. (The credentials are stored in the firmware, encrypted by the crypt function.)

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-284 (Improper Access Control)

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

It affects 2 products.


Products: Baicells Rtd Firmware, Baicells Rts Firmware.

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

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

## Is CVE-2023-24022 being exploited?

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

## Other vulnerabilities in Baicells Nova 227

- [CVE-2023-24508](https://insights.sbomify.com/CVE-2023-24508/): Remote Code Execution in Baicells RTS Platform (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-24022 is a critical vulnerability in Baicells Nova 227, published on 24 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-24022 in the wild and no public exploit code.

Affected product: Baicells Nova 227. 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-24022/ (Markdown: https://insights.sbomify.com/CVE-2023-24022/index.md)
```

## Sources

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

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