CVE-2018-0507
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 FLET'S VIRUS CLEAR Easy Setup & Application Tool ver.11 and earlier versions, FLET'S VIRUS CLEAR v6 Easy Setup & Application Tool ver.11 and earlier versions allow 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 confidenceThe FLET'S VIRUS CLEAR Easy Setup & Application Tool suffers from an untrusted search path vulnerability where the application loads DLLs without specifying full paths, allowing attackers to place malicious Trojan horse DLLs in directories that are searched before legitimate locations. This enables privilege escalation as the application executes the attacker's code with its own privileges.
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= 11= 11CVSS 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.
-
Confirm software installationCheck for presence of 'Ntt East Flet's Virus Clear Easy Setup & Application Tool' or 'Ntt East Flet's Virus Clear V6 Easy Setup & Application Tool' in Windows Programs and Features or registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallAffected if The software is not listed in installed programs, meaning the product is not present
-
Verify exact version numberLocate the application in Programs and Features and note the version column, or right-click the main executable (typically 'VCSuite.exe' or similar) and check its File Properties for the version infoAffected if Version is listed as 11 (exact match to affected version)
-
Inspect application directory permissionsRight-click the application's install folder (usually in C:\Program Files\ or C:\Program Files (x86)\), go to Properties > Security, and verify which users have Write or Modify permissionsAffected if Users other than Administrators have Write or Modify permissions to the application directory, allowing DLL planting
-
Check current user PATH environment variableOpen System Properties > Environment Variables, examine the PATH variable for the current user, and note any directories that are writable by other users or processesAffected if User PATH contains directories that are writable by untrusted users, enabling PATH hijacking of DLLs
The environment is affected if Flet's Virus Clear version 11 is installed AND the application directory or user PATH contains writable directories accessible to untrusted users or processes.
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 dataApply vendor patch if available; otherwise, remove the vulnerable software or ensure the application directory is not writable by unprivileged users and that no untrusted directories appear in the DLL search path.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0507 — 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-2018-0507 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