LiveActive security incident?Get immediate response
CVE Record

CVE-2020-37050: Quick Player 1.3 - '.m3l' Buffer Overflow

Quick Player 1.3 contains a buffer overflow vulnerability that allows attackers to execute arbitrary code by crafting a malicious .m3l file with carefully constructed payload. Attackers can trigger the vulnerability by loading a specially crafted file through the application's file loading mechanism, potentially enabling remote code execution.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Quick Player 1.3 has a buffer overflow in handling .m3l playlist files. A malicious file could allow code execution on a vulnerable endpoint. Business urgency is highest where this old player is installed and users can receive or open untrusted media files.

Executive priority

Treat as targeted endpoint risk, not a broad network emergency. If Quick Player 1.3 exists in the environment, remove or isolate it promptly because public exploit material is available and impact can be full code execution.

Technical view

CVE-2020-37050 is a CWE-120 buffer overflow in M.J.M Soft Quick Player 1.3. Sources describe arbitrary code execution via a specially crafted .m3l file loaded by the application. The bundle lists CVSS 3.1 score 9.8 critical, with public exploit and PoC references.

Likely exposure

Exposure appears limited to endpoints running Quick Player 1.3. This is a client-side file parsing issue, so practical risk depends on users opening attacker-supplied .m3l files or having the application associated with those files.

Exploitation context

Public exploit material exists on ExploitDB and archived researcher content. The provided data does not show CISA KEV listing or confirmed active exploitation. The described trigger is loading a crafted .m3l file through the application.

Researcher notes

There is a notable evidence mismatch: the CVSS vector indicates no user interaction, while the description says exploitation occurs when a crafted file is loaded. No vendor patch is named in the supplied sources; validate with vendor guidance before claiming a fixed version.

Mitigation direction

  • Inventory endpoints for Quick Player 1.3.
  • Remove Quick Player 1.3 where it is not business-required.
  • Check vendor or trusted advisory guidance for any supported update.
  • Block or quarantine untrusted .m3l attachments and downloads where feasible.
  • Restrict file associations that auto-open .m3l files with Quick Player.

Validation and detection

  • Confirm whether Quick Player 1.3 is installed on managed endpoints.
  • Check endpoint software inventories and application control records.
  • Review file association settings for .m3l files.
  • Look for recent .m3l downloads or email attachments in telemetry.
  • Verify controls block untrusted playlist files where policy allows.
Prepared
Confidence
medium
Sources
7

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-120: 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
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-37050 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
6Source 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-37050Attack 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
M.J.M SoftQuick Player1.3Listed
Weakness

CWE details

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

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.