Security readout for executives and security teams
Plain-English summary
CVE-2019-14371 is a denial-of-service style issue in Libav 12.3. A media probing function can enter an infinite loop when handling certain MOV-related data. The available sources do not provide CVSS, CWE, a named fix, or evidence of active exploitation.
Executive priority
Do not treat this as a confirmed active-exploitation emergency from the provided evidence. Prioritize it where business services accept external media, because an infinite loop can degrade availability.
Technical view
The CVE describes an infinite loop in `mov_probe` in `libavformat/mov.c`, related to offset and tag handling. Impact is most plausibly resource exhaustion during media file probing. The source bundle identifies Libav 12.3, but structured affected-product metadata is incomplete.
Likely exposure
Exposure is most likely in services, applications, or appliances that use Libav 12.3 to inspect or ingest untrusted media files. Downstream packages may bundle Libav, so package and container inventory matters.
Exploitation context
The provided sources do not show KEV listing, public exploitation, or weaponized exploit details. Risk depends on whether attackers can submit media files to a Libav-backed processing path.
Researcher notes
Evidence is narrow: CVE text and the Libav Bugzilla reference identify the function and symptom, but omit CVSS, CWE, detailed affected ranges, and remediation status. Avoid assuming impact beyond denial of service without further vendor confirmation.
Mitigation direction
- Inventory direct and bundled Libav usage across applications and containers.
- Check Libav Bugzilla and distribution advisories for official fixes or backports.
- Prioritize systems that process user-supplied media files.
- Restrict untrusted media ingestion where Libav 12.3 remains in use.
- Apply processing timeouts and resource limits around media probing pipelines.
Validation and detection
- Confirm whether any deployed component uses Libav 12.3.
- Review media ingestion paths for attacker-controlled file uploads or feeds.
- Check vendor and distribution package notes for CVE-2019-14371 handling.
- Look for stalled or long-running media probe jobs in monitoring data.
- Document uncertainty where product metadata or fix status is unavailable.
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-2019-14371 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://bugzilla.libav.org/show_bug.cgi?id=1163CVE 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.