CVE-2018-6687
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 · uneditedLoop with Unreachable Exit Condition ('Infinite Loop') in McAfee GetSusp (GetSusp) 3.0.0.461 and earlier allows attackers to DoS a manual GetSusp scan via while scanning a specifically crafted file . GetSusp is a free standalone McAfee tool that runs on several versions of Microsoft Windows.
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 confidenceMcAfee GetSusp versions 3.0.0.461 and earlier contain an infinite loop vulnerability in the file scanning engine. When GetSusp scans a specifically crafted malicious file, the scanning loop enters an unreachable exit condition, causing the tool to hang and resulting in a denial of service condition for the manual scan 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 data<= 3.0.0.461CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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.
-
Locate the GetSusp installation directoryOpen File Explorer and navigate to the default installation path, typically C:\Program Files\McAfee\GetSusp or C:\Program Files (x86)\McAfee\GetSusp. Confirm the getsusp.exe file exists.Affected if GetSusp is installed on the system at all
-
Check GetSusp version from executable propertiesRight-click on getsusp.exe in the installation directory, select Properties, then go to the Details tab. Note the Product version field.Affected if The product version displayed is 3.0.0.461 or lower (for example, 3.0.0.461, 3.0.0.400, 2.0.x.x, etc.)
-
Check installed program version via WindowsOpen Control Panel > Programs and Features (or Settings > Apps & Features on Windows 10). Locate McAfee GetSusp in the list and note the Version column.Affected if The listed version is 3.0.0.461 or earlier
-
Verify scanning functionality is enabledLaunch GetSusp and confirm the scanning engine is active. The vulnerability triggers specifically during file scanning operations, so check if manual or automatic scanning is configured.Affected if GetSusp scanning is actively used or configured to scan untrusted files
The system is affected if McAfee GetSusp version 3.0.0.461 or earlier is installed and the scanning feature is being used to examine files.
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 dataOrganizations should upgrade McAfee GetSusp to a version later than 3.0.0.461 when available. Until a patch is released, avoid scanning untrusted files with GetSusp and consider alternative file analysis methods.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6687 — 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-6687 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