Security readout for executives and security teams
Plain-English summary
This is an old FFmpeg/libavcodec issue where a malicious QuickTime (QT) media file could let an attacker run code when processed by a vulnerable version before FFmpeg 0.11. Business risk depends on whether any systems still parse untrusted media with that legacy library.
Executive priority
Treat as a legacy RCE cleanup item with high impact but exposure-dependent urgency. Prioritize environments that accept or transform customer, partner, or internet-sourced media files.
Technical view
CVE-2012-5360 affects libavcodec in FFmpeg before 0.11. The public description says remote attackers can execute arbitrary code using a crafted QT file. The source bundle does not provide CVSS, CWE, detailed affected package inventory, exploit details, or vendor-specific remediation beyond the version boundary.
Likely exposure
Most exposure is likely in legacy media-processing stacks, appliances, embedded products, or applications bundled with FFmpeg/libavcodec older than 0.11. Modern systems are less likely affected unless they carry outdated static builds or vendor-forked binaries.
Exploitation context
The provided sources do not show CISA KEV listing or confirmed active exploitation. The attack scenario requires a vulnerable media parser to open or process a crafted QT file from an attacker-controlled or untrusted source.
Researcher notes
Evidence is sparse in the supplied bundle: no CVSS vector, CWE, affected CPEs, patch commit, or exploit confirmation is provided. Analysis should stay anchored to FFmpeg before 0.11 and crafted QT file processing.
Mitigation direction
- Inventory FFmpeg and libavcodec versions across servers, endpoints, containers, and embedded products.
- Upgrade any FFmpeg/libavcodec build older than 0.11 following vendor guidance.
- Restrict untrusted QT/media file ingestion on systems that cannot be upgraded promptly.
- Check third-party applications that bundle FFmpeg rather than relying only on OS package versions.
Validation and detection
- Confirm whether any deployed FFmpeg/libavcodec version is older than 0.11.
- Identify services, queues, or user workflows that process externally supplied QT files.
- Review vendor advisories for bundled or forked FFmpeg components in commercial products.
- Verify compensating controls block or isolate untrusted media processing where upgrades are delayed.
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.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2012-5360 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://docs.microsoft.com/en-us/security-updates/VulnerabilityResearchAdvisories/2012/msvr12-017CVE reference · x_refsource_MISC
- https://www.ffmpeg.org/security.htmlCVE reference · x_refsource_CONFIRM
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.