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

> Attackers can exploit a hardcoded SQL Server password to execute remote code and exfiltrate data from Natus NeuroWorks and SleepWorks systems.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-85qp-mxrm-pxg7

## What is CVE-2023-47800?

CVE-2023-47800 is a critical vulnerability in n/a, published on 10 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Natus NeuroWorks and SleepWorks before 8.4 GMA3 utilize a default password of xltek for the Microsoft SQL Server service sa account, allowing a threat actor to perform remote code execution, data exfiltration, or other nefarious actions such as tampering with data or destroying/disrupting MSSQL services.

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

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

It affects 2 products.


Products: Natus Neuroworks Eeg, Natus Sleepworks.

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

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

## Is CVE-2023-47800 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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