# CVE-2023-52043: Weak cryptography in n/a

> Truncated WPA-PSK passwords in D-Link mesh systems allow attackers to bypass authentication and gain unauthorized network access.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Apr 2024
- **Updated:** 6 Sep 2024
- **Also known as:** GHSA-qj6m-mjm6-q6qr

## What is CVE-2023-52043?

CVE-2023-52043 is a high-severity vulnerability in n/a, published on 3 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in D-Link COVR 1100, 1102, 1103 AC1200 Dual-Band Whole-Home Mesh Wi-Fi System (Hardware Rev B1) truncates Wireless Access Point Passwords (WPA-PSK) allowing an attacker to gain unauthorized network access via weak authentication controls.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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


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

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

## Is CVE-2023-52043 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-52043 is a high-severity vulnerability in n/a, published on 3 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-52043 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-52043/ (Markdown: https://insights.sbomify.com/CVE-2023-52043/index.md)
```

## Sources

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

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