CVE-2017-10830
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 · uneditedUntrusted search path vulnerability in Security Setup Tool all versions 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 confidenceThis is a DLL hijacking vulnerability in the Security Setup Tool where the application loads DLLs from directories that an attacker can control (untrusted search path). An attacker can place a malicious Trojan horse DLL in a directory that gets searched before legitimate locations, causing the application to load and execute the attacker's code with the privileges of the running process.
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 dataall versionsCVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Ntt Security Setup Tool is installedLook for the application in typical installation directories such as C:\Program Files\Ntt or check Windows Add/Remove Programs for Ntt Security Setup ToolAffected if The application is present on the system
-
Locate the main executableFind the primary .exe file for the Security Setup Tool, commonly named setup.exe, securitysetup.exe, or similar within the application folderAffected if The executable exists on the system
-
Check for weak directory permissionsReview permissions on the application installation directory and parent directories using icacls or file explorer to determine if unprivileged users can create or write filesAffected if Users without admin rights can write to directories in the application path hierarchy
-
Identify DLL search path behaviorUse a tool like Process Monitor or analyze the application with dependency walking tools to observe which directories it searches for DLLs at runtimeAffected if The application searches directories that are user-writable before system directories
-
Verify DLL preloading riskCheck if the application directory or any directory in the PATH is writable by non-admin users, which would allow placement of malicious DLLs with common namesAffected if A writable directory exists on the DLL search path that precedes system directories
If Ntt Security Setup Tool is installed and any directory in its search path is writable by unprivileged users, the system is vulnerable to DLL hijacking attacks.
Generated from the published advisory. Verify against your own configuration.
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 dataFix the DLL search path vulnerability by using full paths for DLL loading, removing unsafe directories from the search path, or implementing secure DLL loading functions (SetDllDirectory, LOAD_WITH_ALTERED_SEARCH_PATH) to restrict where DLLs can be loaded from.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10830 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-10830 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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