CVE-2017-9662
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 · uneditedAn Improper Privilege Management issue was discovered in Fuji Electric Monitouch V-SFT versions prior to Version 5.4.43.0. Monitouch V-SFT is installed in a directory with weak access controls by default, which could allow an authenticated attacker with local access to escalate privileges.
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 confidenceFuji Electric Monitouch V-SFT versions prior to 5.4.43.0 are installed in a directory with weak access controls by default, which could allow an authenticated local attacker to modify executable files and escalate privileges to SYSTEM or administrative levels.
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<= 5.4.42.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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.
-
Confirm Monitouch V-SFT installationLook for 'Monitouch V-SFT' or 'V-SFT' in the list of installed programs via Windows Control Panel > Programs and Features, or check for the software's installation folder on the system.Affected if The software is present on the system.
-
Identify installed versionLocate the V-SFT installation directory (typically under C:\Program Files\Fuji Electric or similar), then right-click the main executable (such as V-SFT.exe) and view Properties > Details to find the File Version.Affected if The version shown is 5.4.42.0 or earlier.
-
Verify default directory access controlsRight-click the V-SFT installation folder, select Properties > Security tab, and examine the permissions for Users or Authenticated Users groups. Check if these groups have Write or Modify permissions.Affected if Users orAuthenticated Users have Write or Modify permissions to the installation directory.
-
Test executable modification capabilityAs a non-administrator user, attempt to create or modify a file within the V-SFT installation directory, or check if existing .exe files are writable by examining folder permissions.Affected if Low-privilege users can write or modify files in the installation directory.
The system is affected if Monitouch V-SFT version 5.4.42.0 or earlier is installed and the installation directory grants Write or Modify permissions to standard users, allowing potential privilege escalation.
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 dataUpgrade Monitouch V-SFT to version 5.4.43.0 or later which includes proper directory access controls to prevent unauthorized file modification by low-privilege users.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9662 — 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-9662 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