Security readout for executives and security teams
Plain-English summary
CVE-2020-35979 is a heap-based buffer overflow in GPAC 0.8.0 and 1.0.1. GPAC is media-processing software, so exposure matters where systems process media content. The provided sources do not include a CVSS score, confirmed exploitation, or full affected-product mapping.
Executive priority
Treat this as an inventory and remediation item for media-processing environments. Business urgency is highest where GPAC handles untrusted media, but the public evidence provided does not prove active exploitation or assign a severity score.
Technical view
The flaw is reported in gp_rtp_builder_do_avc() within ietf/rtp_pck_mpeg4.c. It is a heap-based buffer overflow in GPAC’s AVC RTP packetization path. A GitHub issue and fixing commit are referenced, but the provided evidence does not define exploit prerequisites or downstream impacted products.
Likely exposure
Organizations may be exposed if they run GPAC 0.8.0 or 1.0.1, or software embedding those GPAC versions, especially in media-processing pipelines. The source bundle does not identify CPEs, packaged distributions, or affected downstream products.
Exploitation context
The CVE is not listed as KEV in the source bundle, and no cited source confirms active exploitation. The issue type is memory corruption, but trigger conditions, attacker position, and practical exploitability are not established in the provided evidence.
Researcher notes
The public record is sparse: affected versions are named, the vulnerable function and file are identified, and a fixing commit is referenced. Missing details include CVSS, CWE mapping, precise trigger conditions, and downstream package impact.
Mitigation direction
- Inventory GPAC installations and embedded GPAC libraries.
- Upgrade to a maintained GPAC release containing the referenced fix.
- If upgrade timing is unclear, check current GPAC vendor guidance.
- Limit untrusted media processing until fixed status is confirmed.
- Track the CVE record and GPAC issue for updated affected-version guidance.
Validation and detection
- Confirm whether GPAC 0.8.0 or 1.0.1 exists in the environment.
- Check builds for the referenced fixing commit or newer maintained release.
- Review media-processing services that use AVC RTP packetization paths.
- Verify software bills of materials for embedded GPAC components.
- Document compensating controls for any unfixed media-processing systems.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
CVE-2020-35979 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/gpac/gpac/issues/1662CVE reference · x_refsource_MISC
- https://github.com/gpac/gpac/commit/b15020f54aff24aaeb64b80771472be8e64a7adcCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.