LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36936: Magic Mouse 2 utilities 2.20 - 'magicmouse2service' Unquoted Service Path

Magic Mouse 2 Utilities 2.20 contains an unquoted service path vulnerability in its Windows service configuration. Attackers can exploit the unquoted path to inject malicious executables and gain elevated system privileges by placing a malicious file in the service path.

HighCVSS 8.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-36936 is a local privilege-escalation issue in Magic Mouse 2 Utilities 2.20 for Windows. A low-privileged user could abuse an improperly configured Windows service path to run code with higher privileges. This is important for endpoints where the software is installed, but it is not described as remotely exploitable.

Executive priority

Prioritize remediation on managed Windows endpoints where the product is installed, especially shared or high-value workstations. This is not a remote internet-facing flaw, but it can turn a low-privileged foothold into administrative control on affected machines.

Technical view

Magic Mouse 2 Utilities 2.20 configures the Windows service 'magicmouse2service' with an unquoted service path, mapped to CWE-428. The CVSS 4.0 score is 8.5. The attack vector is local, requires low privileges, and no user interaction. Successful exploitation can affect confidentiality, integrity, and availability of the local system.

Likely exposure

Exposure is limited to Windows systems running Magic Mouse 2 Utilities version 2.20 with the vulnerable service configuration. Risk is highest on shared workstations, developer machines, kiosks, or other endpoints where standard users can write to relevant service path locations.

Exploitation context

The source bundle includes an ExploitDB reference, indicating public exploit information exists. CISA KEV status is false in the provided data, and no cited source states active exploitation. Treat this as a credible local escalation risk, not evidence of ongoing attacks.

Researcher notes

Evidence identifies one affected version: Magic Mouse 2 Utilities 2.20. The provided sources do not name a vendor patch, fixed version, or active exploitation. Validation should focus on service configuration, installed version, and writable directories along the unquoted service path.

Mitigation direction

  • Inventory endpoints for Magic Mouse 2 Utilities version 2.20.
  • Check vendor guidance for fixed versions or supported remediation.
  • Upgrade or remove the software where business use is not required.
  • Harden the Windows service path configuration after change-control review.
  • Restrict standard-user write access to service path directories.

Validation and detection

  • Confirm whether Magic Mouse 2 Utilities 2.20 is installed.
  • Inspect the 'magicmouse2service' configuration for an unquoted executable path.
  • Review permissions on directories in the service path.
  • Verify remediation by confirming the service path is safely configured.
  • Check endpoint telemetry for suspicious service-related process launches.
Prepared
Confidence
high
Sources
5

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-428: 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-36936 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.5 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

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
4Source 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.5CVSS 4.0HighCVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:NPrimary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

8.5High
CVSS 4.0 vector shape for CVE-2020-36936Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Magic UtilitiesMagic Mouse 2 utilities2.20Listed
Weakness

CWE details

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