Encryption DesktopApplication · Symantec

CVE-2016-6590

HIGH · 7.8 CVSS v3.1 Published 2020-01-08
Fix available
A fix is available. Upgrade to 7.6 / 10.4.1 or later.
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
A privilege escalation vulnerability exists when loading DLLs during boot up and reboot in Symantec IT Management Suite 8.0 prior to 8.0 HF4 and Suite 7.6 prior to 7.6 HF7, Symantec Ghost Solution Suite 3.1 prior to 3.1 MP4, Symantec Endpoint Virtualization 7.x prior to 7.6 HF7, and Symantec Encryption Desktop 10.x prior to 10.4.1, which could let a local malicious user execute arbitrary code.

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 confidence

This is a DLL hijacking vulnerability during boot/reboot in multiple Symantec products. The affected software loads DLLs from locations where a local attacker can place a malicious DLL, achieving arbitrary code execution with elevated privileges.

MitigationApply the vendor-supplied hotfixes: IT Management Suite 8.0 to HF4, Suite 7.6 to HF7, Ghost Solution Suite 3.1 to MP4, Endpoint Virtualization 7.x to HF7, and Encryption Desktop to version 10.4.1.

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
Encryption DesktopApplication
Affected:>= 10.0.0, < 10.4.1
Endpoint EncryptionApplication
Affected:>= 7.0, < 7.6= 7.6
Ghost Solution SuiteApplication
Affected:= 3.1
It Management SuiteApplication
Affected:= 7.6= 8.0

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. Identify installed Symantec product
    Open Windows Control Panel, go to Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | DisplayName' to list installed software. Look for Symantec Encryption Desktop, Symantec Endpoint Encryption, Symantec Ghost Solution Suite, or Symantec IT Management Suite.
    Affected if Any of these four affected products are listed as installed
  2. Check Symantec Encryption Desktop version
    If installed, locate the application in Programs and Features to view the version, or check the application's About/Help section for the version number.
    Affected if Version is 10.0.0 or higher but lower than 10.4.1
  3. Check Symantec Endpoint Encryption version
    If installed, locate the application in Programs and Features to view the version, or check the application's About/Help section for the version number.
    Affected if Version is 7.0 or higher through 7.6 (any version in this range)
  4. Check Symantec Ghost Solution Suite version
    If installed, locate the application in Programs and Features to view the version, or check the application's About/Help section for the version number.
    Affected if Version is exactly 3.1
  5. Check Symantec IT Management Suite version
    If installed, locate the application in Programs and Features to view the version, or check the application's About/Help section for the version number.
    Affected if Version is exactly 7.6 or exactly 8.0

A system is affected if any of the four listed Symantec products is installed and its version matches the specific vulnerable version range for that product.

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
Upgrade available Upgrade to 7.6 / 10.4.1 or later
Fixed in 7.610.4.1
Interim mitigation

Apply the vendor-supplied hotfixes: IT Management Suite 8.0 to HF4, Suite 7.6 to HF7, Ghost Solution Suite 3.1 to MP4, Endpoint Virtualization 7.x to HF7, and Encryption Desktop to version 10.4.1.

Fix this in Encryption Desktop Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-6590 — 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-2016-6590 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