LiveActive security incident?Get immediate response
CVE Record

CVE-2021-28580: Medium by Adobe file parsing buffer overflow vulnerability could lead to arbitrary code execution

Medium by Adobe version 2.4.5.331 (and earlier) is affected by a buffer overflow vulnerability when parsing a crafted file. An unauthenticated attacker could leverage this vulnerability to achieve remote code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-28580 affects Medium by Adobe 2.4.5.331 and earlier. A malicious file can trigger a buffer overflow when opened, potentially letting an attacker run code as the current user. The main business risk is compromise of workstations where users handle untrusted files.

Executive priority

Treat this as a high-priority endpoint remediation item where Adobe Medium is present. It is not described as actively exploited, but successful exploitation could give an attacker control in the user context.

Technical view

The issue is a CWE-120 buffer overflow in Medium by Adobe file parsing. It is remotely reachable through a crafted file, requires no authentication, but requires user interaction. CVSS 3.1 is 8.8 with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to systems with Medium by Adobe 2.4.5.331 or earlier installed, especially endpoints where users may open files from external or untrusted sources.

Exploitation context

The source bundle does not show CISA KEV listing or evidence of active exploitation. Exploitation requires convincing a user to open a malicious file, so phishing and file-sharing workflows are the most relevant risk paths.

Researcher notes

The available evidence identifies the vulnerable product, version boundary, weakness class, impact, and user-interaction requirement. The bundle does not provide exploit-in-the-wild evidence, detailed root cause, or a named fixed version.

Mitigation direction

  • Inventory endpoints for Medium by Adobe installations and versions.
  • Prioritize remediation for version 2.4.5.331 and earlier.
  • Review Adobe APSB21-34 and apply vendor guidance.
  • Limit opening untrusted Medium files until remediation is confirmed.
  • Use endpoint controls to reduce impact from suspicious file execution.

Validation and detection

  • Confirm whether Medium by Adobe is installed on managed endpoints.
  • Verify installed versions are not 2.4.5.331 or earlier.
  • Check Adobe APSB21-34 for the vendor-supported remediation path.
  • Review security telemetry for suspicious file-open events involving Medium.
  • Document exceptions where affected versions cannot be remediated immediately.
Prepared
Confidence
medium
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-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-2021-28580 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.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
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.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2021-28580Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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
AdobeMediumunspecified, unspecifiedListed
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.