LiveActive security incident?Get immediate response
CVE Record

CVE-2012-5359: Libavcodec in FFmpeg before 0.11 allows remote attackers to execute arbitrary code via a crafted ASF file.

Libavcodec in FFmpeg before 0.11 allows remote attackers to execute arbitrary code via a crafted ASF file.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is an older FFmpeg Libavcodec flaw where a malicious ASF media file could lead to arbitrary code execution in versions before 0.11. Business risk is highest where servers or applications automatically ingest, preview, transcode, or scan untrusted media files.

Executive priority

Prioritize remediation if the organization processes user-supplied media or operates legacy media services. The impact is potentially severe, but urgency depends on whether vulnerable FFmpeg versions remain in active workflows.

Technical view

CVE-2012-5359 affects Libavcodec in FFmpeg before 0.11. The public description states that a crafted ASF file can allow remote arbitrary code execution. The provided sources do not include CVSS, CWE, vulnerable code details, exploit maturity, or downstream package matrices.

Likely exposure

Exposure is likely limited to systems still using FFmpeg or bundled Libavcodec before 0.11 to process untrusted ASF files. Check embedded software, media pipelines, upload processors, and vendor-packaged applications that may include old FFmpeg builds.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. The attack model is file-based remote code execution: an attacker needs a target workflow that opens or processes a crafted ASF file with a vulnerable FFmpeg version.

Researcher notes

The source data is sparse: affected metadata is listed as n/a, severity is unknown, and no CWE or CVSS is provided. Treat the FFmpeg before-0.11 version statement as the primary exposure anchor and avoid assuming exploit availability.

Mitigation direction

  • Upgrade FFmpeg/Libavcodec to version 0.11 or later where applicable.
  • Check operating system or appliance vendor advisories for backported fixes.
  • Restrict untrusted ASF file ingestion until affected components are remediated.
  • Run media processing workloads with least privilege and isolation.
  • Inventory bundled FFmpeg copies inside third-party applications.

Validation and detection

  • Identify installed and bundled FFmpeg/Libavcodec versions across media-processing systems.
  • Confirm whether any version is older than FFmpeg 0.11.
  • Review upload, transcoding, scanning, and preview workflows for ASF handling.
  • Verify vendor package changelogs or advisories for this CVE or equivalent backport.
  • Confirm no internet-facing workflow automatically processes untrusted ASF files.
Prepared
Confidence
medium
Sources
4

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.

description · low confidence lookup

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 lookup
cve · low confidence lookup

CVE-2012-5359 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
3Source 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.