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

> Predictable default WPA2 PSKs in Arris devices allow attackers to gain unauthorized remote access to the network.

- **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:** 27 Dec 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-f4gg-hh5p-pjmg

## What is CVE-2023-40038?

CVE-2023-40038 is a high-severity vulnerability in n/a, published on 27 Dec 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Arris DG860A and DG1670A devices have predictable default WPA2 PSKs that could lead to unauthorized remote access. (They use the first 6 characters of the SSID and the last 6 characters of the BSSID, decrementing the last digit.)

Weakness: CWE-287 (Improper Authentication)

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

It affects 2 products.


Products: Arris Dg1670a Firmware, Arris Dg860a Firmware.

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

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

## Is CVE-2023-40038 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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