Fall Creators UpdateApplication · Ntt West

CVE-2018-16177

HIGH · 7.8 CVSS v3.1 Published 2019-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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
Untrusted search path vulnerability in The installer of Windows 10 Fall Creators Update Modify module for Security Measures tool allows an attacker to gain privileges via a Trojan horse DLL in an unspecified directory.

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 · moderate confidence

This is a DLL hijacking/untrusted search path vulnerability in the Windows 10 Fall Creators Update Modify module installer for the Security Measures tool. The installer searches an unspecified directory that an attacker can control, allowing a malicious Trojan horse DLL to be loaded with elevated privileges during the installation process.

MitigationUsers should only obtain this installer from official Microsoft sources and ensure they are running patched versions. The vendor fix requires modifying the installer to use secure DLL search paths (e.g., specifying full paths to DLLs or enabling SafeDllSearchMode) and validating DLL signatures before loading.

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
Fall Creators UpdateApplication
Affected:all versions

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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. Locate the Ntt West Fall Creators Update Security Measures installer
    Search for installer executables related to Ntt West Fall Creators Update Security Measures tool on the system. Check common installation directories and download folders.
    Affected if The installer executable is present on the system and has not been patched.
  2. Identify the installer file version
    Right-click the installer executable, select Properties, and examine the Version tab for file version and product version information.
    Affected if The installed version falls within the Ntt West Fall Creators Update range and has not been updated to include secure DLL search paths.
  3. Inspect the installer DLL search behavior
    Run the installer while monitoring DLL loading using Process Monitor (filter by the installer process name), observe which directories the installer searches for DLLs.
    Affected if The installer loads DLLs from directories writable by non-privileged users or uncontrolled locations (untrusted search path).
  4. Verify DLL signature validation
    Monitor the installer process for DLL loading events and check whether loaded DLLs have valid digital signatures using sigcheck or similar tool.
    Affected if The installer loads DLLs without verifying signatures, allowing malicious DLLs to be loaded.
  5. Check for presence of vulnerable installer
    Search for any executable files from Ntt West related to the Security Measures tool in Program Files, Program Files (x86), or user download directories.
    Affected if A vulnerable version of the installer exists on the system and can be executed.

The environment is affected if the Ntt West Fall Creators Update Security Measures installer with the untrusted DLL search path vulnerability is present and executable on the system.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Users should only obtain this installer from official Microsoft sources and ensure they are running patched versions. The vendor fix requires modifying the installer to use secure DLL search paths (e.g., specifying full paths to DLLs or enabling SafeDllSearchMode) and validating DLL signatures before loading.

Fix this in Fall Creators Update Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2018-16177 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