LiveActive security incident?Get immediate response
CVE Record

CVE-2019-20171: An issue was discovered in GPAC version 0.5.2 and 0.9.0-development-20191109.

An issue was discovered in GPAC version 0.5.2 and 0.9.0-development-20191109. There are memory leaks in metx_New in isomedia/box_code_base.c and abst_Read in isomedia/box_code_adobe.c.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2019-20171 describes memory leaks in GPAC media parsing code. The practical concern is service degradation or resource exhaustion where vulnerable GPAC builds process media files. The source bundle gives no CVSS score, no CISA KEV listing, and no active-exploitation evidence.

Executive priority

Treat this as a dependency hygiene and availability risk, not an emergency based on current evidence. Prioritize remediation where GPAC handles untrusted media or runs in always-on production pipelines.

Technical view

The issue affects GPAC 0.5.2 and 0.9.0-development-20191109. Reported leak locations are metx_New in isomedia/box_code_base.c and abst_Read in isomedia/box_code_adobe.c. Available sources characterize this as memory leakage; they do not show code execution, privilege escalation, or confirmed exploitation.

Likely exposure

Exposure is most likely in systems that directly run the named GPAC versions or distribution packages derived from them, especially automated media inspection, conversion, or parsing workflows. Evidence is incomplete for other products or embedded uses.

Exploitation context

The bundle does not cite active exploitation, and kev is false. The likely threat model is crafted or malformed media input causing repeated memory loss during parsing, but the sources do not provide exploitability detail or operational evidence.

Researcher notes

The record is sparse: no CVSS, CWE, CPE, or exploit status is provided. Analysis should stay tied to the two named functions, the two named GPAC versions, and the Debian security update reference.

Mitigation direction

  • Apply the Debian LTS gpac security update where applicable.
  • Identify and remove GPAC 0.5.2 and the named 0.9.0 development build.
  • Check current GPAC or OS vendor guidance for fixed packages.
  • Limit untrusted media processing until vulnerable builds are replaced.

Validation and detection

  • Inventory installed GPAC versions across servers, containers, and build images.
  • Review media-processing services for GPAC dependency usage.
  • Confirm Debian systems received the relevant DLA 2072-1 update.
  • Monitor affected services for abnormal memory growth during media parsing.
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.

cve · low confidence lookup

CVE-2019-20171 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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