# CVE-2023-6514: Auth bypass in AJMD-370S

> Attackers can bypass Bluetooth identity authentication to access restricted functions on Huawei Smart Screen devices.

- **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:** 6 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-6rmr-87cv-5h7f

## What is CVE-2023-6514?

CVE-2023-6514 is a high-severity authentication bypass vulnerability in Huawei AJMD-370S, published on 6 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Bluetooth module of some Huawei Smart Screen products has an identity authentication bypass vulnerability. Successful exploitation of this vulnerability may allow attackers to access restricted functions. 

Successful exploitation of this vulnerability may allow attackers to access restricted functions.

Weakness: CWE-287 (Improper Authentication), CWE-840

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

It affects 1 product.


Products: Huawei Ajmd-370s Firmware.

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

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

## Is CVE-2023-6514 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-6514 is a high-severity authentication bypass vulnerability in Huawei AJMD-370S, published on 6 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-2023-6514 in the wild and no public exploit code.

Affected product: Huawei AJMD-370S. 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-6514/ (Markdown: https://insights.sbomify.com/CVE-2023-6514/index.md)
```

## Sources

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

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