# CVE-2017-15366: Hardcoded credentials in n/a

> Attackers can gain full admin access to NDoc servers and clients by using default credentials exposed in cleartext log files during installation.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 26 Oct 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-rfvg-559m-h7mr

## What is CVE-2017-15366?

CVE-2017-15366 is a critical vulnerability in n/a, published on 26 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Before Thornberry NDoc version 8.0, laptop clients and the server have default database (Cache) users set up with a single password. This password is left behind in a cleartext log file during client installation on laptops. This password can be used to gain full admin/system access to client devices (if no firewall is present) or the NDoc server itself. Once the password is known to an attacker, local access is not required.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2017-15366?

It affects 1 product.


Products: Ndocsoftware Ndoc.

## How do I fix CVE-2017-15366?

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

## Is CVE-2017-15366 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-15366 and fix it if it is affected.

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

## Sources

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

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