LiveActive security incident?Get immediate response
CVE Record

CVE-2019-20016: libmysofa before 2019-11-24 does not properly restrict recursive function calls, as demonstrated by reports...

libmysofa before 2019-11-24 does not properly restrict recursive function calls, as demonstrated by reports of stack consumption in readOHDRHeaderMessageDatatype in dataobject.c and directblockRead in fractalhead.c. NOTE: a download of v0.9 after 2019-12-06 should fully remediate this issue.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2019-20016 is a libmysofa recursion-control flaw. Older code could consume excessive stack while parsing certain data structures. For executives, the likely business impact is service instability where vulnerable libmysofa builds process untrusted audio-related files. The source bundle does not provide CVSS, affected product mapping, or evidence of active exploitation.

Executive priority

Treat as a targeted dependency hygiene issue, not an emergency based on available evidence. Prioritize systems that parse externally supplied files, then update vulnerable libmysofa builds through normal patch management.

Technical view

libmysofa before 2019-11-24 did not properly restrict recursive function calls. The CVE cites stack consumption in readOHDRHeaderMessageDatatype in dataobject.c and directblockRead in fractalhead.c. The record notes that downloading v0.9 after 2019-12-06 should fully remediate the issue.

Likely exposure

Exposure is most plausible in applications or services that embed libmysofa builds from before 2019-11-24, especially where users or external systems supply files parsed by the library. The bundle does not identify downstream products, package names, CPEs, or platform-specific affected versions.

Exploitation context

The provided sources describe reports of stack consumption and a remediation commit. CISA KEV status is false, and the bundle provides no cited evidence of active exploitation, public weaponization, or real-world incident use.

Researcher notes

The evidence is narrow: CVE text, two GitHub issue references, and one upstream commit. No CVSS, CWE, CPE, exploit status, or detailed affected downstream product list is provided. Avoid broad exposure claims without local dependency evidence.

Mitigation direction

  • Inventory applications and packages that include libmysofa.
  • Update libmysofa to code from after 2019-11-24.
  • For v0.9, use a download or package dated after 2019-12-06.
  • Follow upstream or distribution guidance for patched package availability.
  • Limit untrusted file parsing by vulnerable builds until updated.

Validation and detection

  • Confirm whether deployed software links or bundles libmysofa.
  • Check libmysofa source, package, or build date against 2019-11-24.
  • For v0.9 builds, verify package provenance after 2019-12-06.
  • Review ingestion paths that pass external files into libmysofa.
  • Retest affected workflows after updating the dependency.
Prepared
Confidence
medium
Sources
5

Public sources used

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-20016 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.

Source materials

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.