dbcve.org
NdocApplication · Ndocsoftware

CVE-2017-15366

CRITICAL · 9.8 CVSS v3.0 Published 2017-10-26
Fix available
A fix is available. Upgrade to after 7.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Default Cache database credentials are hardcoded in Thornberry NDoc versions before 8.0 and are exposed in cleartext within client installation log files on laptops. Attackers with knowledge of these credentials can authenticate remotely to gain full admin/system-level access to NDoc clients or the server without requiring local access or bypassing firewalls.

MitigationImmediately change default database credentials, remove or redact cleartext passwords from all log files, deploy firewalls to restrict unauthorized access, and upgrade to NDoc version 8.0 or later to eliminate the default credential vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NdocApplication
Affected:<= 7.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed NDoc version
    Check the NDoc application version through the software itself (typically in Help > About) or by locating the version information in the installation directory or Windows Programs and Features
    Affected if The installed version is 7.4 or lower (any version before 8.0)
  2. Locate NDoc installation log files
    Search the system for NDoc installation log files - common locations include the installation directory, user temp folders, or directories where installation logs were saved during client deployment
    Affected if Log files exist from NDoc installation or setup
  3. Search log files for cleartext database credentials
    Open any found NDoc log files and search for keywords such as 'password', 'Cache', 'database', 'credentials', or look for Connection String patterns containing user IDs and passwords in plain text
    Affected if Log files contain any hardcoded database credentials or connection strings with passwords visible in cleartext
  4. Verify if default credentials are still in use
    Check NDoc configuration files or database connection settings to determine if the default Cache database credentials (typically the default Cache user credentials that were shipped with the software) are still active and unchanged
    Affected if The default database credentials have not been changed from the factory defaults

A user is affected if they are running NDoc version 7.4 or lower AND have installation log files containing cleartext default database credentials that have not been changed from the hardcoded defaults.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 7.4
Interim mitigation

Immediately change default database credentials, remove or redact cleartext passwords from all log files, deploy firewalls to restrict unauthorized access, and upgrade to NDoc version 8.0 or later to eliminate the default credential vulnerability.

Recommended fix High confidence

NDoc 8.0 or later

  1. Backup the current NDoc installation, including all databases and configuration files
  2. Obtain NDoc version 8.0 or later from the official Thornberry vendor source
  3. Install the upgrade following the vendor's documented upgrade procedure
  4. After upgrade, verify that default database (Cache) users have new, unique passwords configured
  5. Confirm that log files no longer contain sensitive credentials in cleartext
  6. Test that client and server communications function correctly post-upgrade
Caveat Specific breaking changes not documented in available materials; exercise standard upgrade precautions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ndoc Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-15366 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-15366 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data