LiveActive security incident?Get immediate response
CVE Record

CVE-2020-37129: Memu Play 7.1.3 - Insecure Folder Permissions

Memu Play 7.1.3 contains an insecure folder permissions vulnerability that allows low-privileged users to modify the MemuService.exe executable. Attackers can replace the service executable with a malicious file during system restart to gain SYSTEM-level privileges by exploiting unrestricted file modification permissions.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Memu Play 7.1.3 reportedly installs with folder permissions that let low-privileged Windows users change the service executable. If abused, the next service restart can run attacker-controlled code as SYSTEM. This is mainly a risk on shared workstations, developer machines, kiosks, or any endpoint where non-admin users can log in locally.

Executive priority

Prioritize remediation if Memu Play 7.1.3 exists on managed endpoints. The issue can turn ordinary local access into full system control. It is less urgent for environments without Memu Play or without shared/local user exposure, but should still be removed or corrected where found.

Technical view

CVE-2020-37129 is an insecure permissions issue in Microvirt Memu Play 7.1.3, mapped to CWE-276. Public descriptions say non-admin users can modify MemuService.exe and gain SYSTEM-level privileges after restart. Although the CVSS vector in the bundle is network/unauthenticated, the described attack path is local privilege escalation.

Likely exposure

Exposure is limited to systems running Memu Play 7.1.3. Risk is highest where untrusted or standard users have local access to the same Windows host. Organizations that do not deploy Android emulators are likely unaffected.

Exploitation context

A public Exploit-DB entry is referenced, so exploit information exists publicly. The source bundle does not show CISA KEV listing or cite active exploitation in the wild. Treat this as a serious local privilege-escalation issue, not confirmed mass exploitation.

Researcher notes

The record contains a notable inconsistency: the supplied CVSS vector implies remote unauthenticated exploitation, while the description and advisory framing indicate local privilege escalation through writable service files. Validate against the CVE and VulnCheck records before scoring internally. No vendor patch details are included in the provided sources.

Mitigation direction

  • Inventory endpoints for Memu Play 7.1.3 installations.
  • Remove Memu Play where it is not business-required.
  • Check Microvirt guidance for fixed versions or supported remediation.
  • Upgrade if the vendor provides a corrected release.
  • Restrict non-admin write access to the Memu Play installation directory.
  • Prioritize shared-user endpoints and systems with sensitive access.

Validation and detection

  • Confirm whether Memu Play 7.1.3 is installed.
  • Review installation directory permissions for non-admin write access.
  • Check whether MemuService.exe is writable by standard users.
  • Verify service runs with SYSTEM or similarly privileged context.
  • Document version, host ownership, and remediation status.
Prepared
Confidence
medium
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-276: 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-37129 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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
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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2020-37129Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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
MicrovirtMemu Play7.1.3Listed
Weakness

CWE details

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

CWE-276 · source CWE mapping

Incorrect Default Permissions

Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.