LiveActive security incident?Get immediate response
CVE Record

CVE-2021-21859: An exploitable integer truncation vulnerability exists within the MPEG-4 decoding functionality of the GPAC...

An exploitable integer truncation vulnerability exists within the MPEG-4 decoding functionality of the GPAC Project on Advanced Content library v1.0.1. The stri_box_read function is used when processing atoms using the 'stri' FOURCC code. An attacker can convince a user to open a video to trigger this vulnerability.

HighCVSS 8.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-21859 is a high-severity flaw in GPAC's MPEG-4 parsing. A malicious video can trigger the issue if a user or system opens it with the affected GPAC library. Business risk is highest where GPAC processes untrusted media uploads, attachments, or third-party videos.

Executive priority

Treat as a high-priority remediation item for any system that processes outside video files. The vulnerability requires a malicious file to be opened or processed, so urgency depends on whether GPAC is exposed to untrusted media.

Technical view

The supplied sources describe an integer truncation vulnerability in GPAC Project Advanced Content v1.0.1 and commit a8a8d412. The vulnerable stri_box_read function processes MPEG-4 atoms with the 'stri' FOURCC code. CVSS 3.0 is 8.8 with network delivery, low complexity, no privileges, and required user interaction.

Likely exposure

Exposure is likely limited to environments using the affected GPAC Project Advanced Content versions to decode or inspect MPEG-4 content. Public-facing upload pipelines, media conversion workers, and desktop workflows handling outside video files deserve priority review.

Exploitation context

The bundle says an attacker can convince a user to open a video to trigger the vulnerability. It does not provide evidence of active exploitation, and the CVE is not marked CISA KEV in the supplied data.

Researcher notes

Evidence in the bundle is sufficient for affected component, trigger surface, and CVSS severity. It does not include exploit details, patch identifiers, or proof of active exploitation. Validation should focus on version provenance and media-processing data flows.

Mitigation direction

  • Inventory GPAC use in media decoding, conversion, preview, and validation workflows.
  • Check GPAC, Debian, and OS vendor guidance for fixed packages or supported updates.
  • Avoid processing untrusted MPEG-4 files with affected GPAC builds until remediated.
  • Run media processing with least privilege and strong process isolation.
  • Restrict or queue external video uploads where affected processing cannot be patched quickly.

Validation and detection

  • Confirm whether deployed GPAC matches v1.0.1 or commit a8a8d412.
  • Map applications and services that call GPAC against user-supplied video content.
  • Review package manager advisories, including Debian DSA-4966, for installed vulnerable packages.
  • Verify remediation by confirming GPAC package or build provenance after update.
  • Check logs for crashes in GPAC-backed MPEG-4 processing jobs.
Prepared
Confidence
high
Sources
4

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-680: 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-2021-21859 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.0)
Known Exploited
No
Published

Vector: CVSS:3.0/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
3Source 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.0HighCVSS:3.0/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.0 score

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

Vector: CVSS:3.0/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
n/aGPAC ProjectGPAC Project Advanced Content commit a8a8d412dabcb129e695c3e7d861fcc81f608304, GPAC Project Advanced Content v1.0.1Listed
Weakness

CWE details

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

CWE-680 · source CWE mapping

Integer Overflow to Buffer Overflow

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