LiveActive security incident?Get immediate response
CVE Record

CVE-2021-39847: XMP Toolkit SDK Stack-based Buffer Overflow Could Lead To Arbitrary Code Execution

XMP Toolkit SDK version 2020.1 (and earlier) is affected by a stack-based buffer overflow vulnerability potentially resulting in arbitrary code execution in the context of the current user. Exploitation requires user interaction in that a victim must open a crafted file.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-39847 is a high-severity memory corruption flaw in Adobe XMP Toolkit SDK 2020.1 and earlier. A crafted file can trigger code execution when opened by a user, so risk is highest where systems process untrusted documents, images, or metadata-bearing files.

Executive priority

Treat as a prioritized patch-management issue for systems that handle untrusted files. It is high impact but requires user interaction, and the provided evidence does not show known active exploitation.

Technical view

The issue is a CWE-121 stack-based buffer overflow in Adobe XMP Toolkit SDK. CVSS 3.0 is 7.8 with local attack vector, low complexity, no privileges required, and required user interaction. Successful exploitation may execute code as the current user with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure likely exists in software or systems embedding Adobe XMP Toolkit SDK 2020.1 or earlier, and in environments using related packaged components referenced by Debian exempi advisories. Confirm actual exposure through dependency, package, and SBOM review rather than product-name assumptions.

Exploitation context

The provided sources say exploitation requires a victim to open a crafted file. The CVE is not listed as CISA KEV in the bundle, and no cited source here establishes active exploitation.

Researcher notes

The main uncertainty is downstream exposure: products embedding the SDK are not enumerated in the bundle. Validation should focus on SDK/package presence and file parsing paths. Avoid assuming exploitability in every Adobe product without evidence.

Mitigation direction

  • Check Adobe APSB21-65 for the fixed XMP Toolkit SDK guidance.
  • Apply relevant Debian LTS exempi security updates where that package is deployed.
  • Inventory applications that parse XMP metadata from user-supplied files.
  • Reduce exposure to untrusted files until affected components are updated.
  • Prioritize endpoints and workflows handling external documents or media.

Validation and detection

  • Search SBOMs and dependency manifests for Adobe XMP Toolkit SDK.
  • Check installed Debian packages for exempi on relevant hosts.
  • Confirm deployed versions are newer than affected 2020.1-and-earlier SDK builds.
  • Review file-ingestion workflows that parse XMP metadata.
  • Verify vendor advisories are mapped to local package or application versions.
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-121: 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-39847 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
7.8 (3.0)
Known Exploited
No
Published

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

Vulnerability scoring details

Base CVSS 3.0 score

7.8High
CVSS 3.0 vector shape for CVE-2021-39847Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:L/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
AdobeXMP Toolkitunspecified, unspecifiedListed
Weakness

CWE details

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

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.