LiveActive security incident?Get immediate response
CVE Record

CVE-2020-7250: ENS symbolic link log file manipulation vulnerability

Symbolic link manipulation vulnerability in McAfee Endpoint Security (ENS) for Windows prior to 10.7.0 February 2020 Update allows authenticated local user to potentially gain an escalation of privileges by pointing the link to files which the user which not normally have permission to alter via carefully creating symbolic links from the ENS log file directory.

HighCVSS 8.2Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-7250 is a local privilege escalation issue in McAfee Endpoint Security for Windows. A logged-in user could abuse symbolic links in the ENS log directory so ENS potentially changes files the user could not normally modify. This matters most on Windows endpoints still running ENS 10.x before the 10.7.0 February 2020 Update.

Executive priority

Treat this as a high-priority endpoint hygiene issue, not an internet-scale emergency. Patch older ENS deployments promptly, especially where endpoints are shared, exposed to untrusted users, or already under investigation for compromise.

Technical view

The issue is CWE-59 symbolic link manipulation in the ENS log file directory. The CVSS 3.1 vector is local, low complexity, low privileges, user interaction required, and changed scope, with high confidentiality, integrity, and availability impact. Sources identify McAfee Endpoint Security for Windows 10.x before 10.7.0 February 2020 Update as affected.

Likely exposure

Exposure is limited to Windows systems running affected McAfee ENS 10.x versions. The attacker needs local authenticated access, so the risk is highest on shared workstations, compromised endpoints, or environments where low-privilege local users can log in.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. This is not described as remotely exploitable. It is still important because local privilege escalation can turn an initial low-privilege foothold into broader endpoint control.

Researcher notes

The source bundle supports the affected product, version boundary, CWE-59 classification, and CVSS vector. It does not provide exploit details, indicators of compromise, or evidence of active exploitation. Avoid assuming impact outside McAfee ENS for Windows 10.x before the February 2020 update.

Mitigation direction

  • Upgrade ENS for Windows to 10.7.0 February 2020 Update or later.
  • Review McAfee security bulletin SB10309 for exact vendor guidance.
  • Prioritize endpoints with shared users or known compromise risk.
  • Limit unnecessary local interactive access on affected Windows systems.
  • Monitor protected-file changes on systems awaiting remediation.

Validation and detection

  • Inventory Windows endpoints running McAfee Endpoint Security.
  • Confirm ENS versions and update levels against the affected range.
  • Verify remediation against McAfee bulletin SB10309.
  • Check whether local non-admin users can access affected systems.
  • Review endpoint logs for unusual protected-file modification events.
Prepared
Confidence
high
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-59: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-7250 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.2 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.2CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H1.56Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.2High
CVSS 3.1 vector shape for CVE-2020-7250Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
McAfee LLCMcAfee Endpoint Security (ENS)10.xListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-59 · source CWE mapping

Improper Link Resolution Before File Access ('Link Following')

Improper Link Resolution Before File Access ('Link Following') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.