LiveActive security incident?Get immediate response
CVE Record

CVE-2014-125012: FFmpeg dxtroy.c integer coercion

A vulnerability was found in FFmpeg 2.0. It has been classified as problematic. Affected is an unknown function of the file libavcodec/dxtroy.c. The manipulation leads to integer coercion error. It is possible to launch the attack remotely. It is recommended to apply a patch to fix this issue.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's Takemoderate

Analyst readout for executives and security teams

Plain-English summary

FFmpeg 2.0 has an integer coercion flaw in libavcodec/dxtroy.c. A remote attacker may be able to trigger a low availability impact when FFmpeg processes crafted media. The sources do not indicate data theft, integrity compromise, or confirmed active exploitation.

Executive priority

Handle as a scheduled remediation item, elevated for systems that process untrusted media at scale or from the internet. It is not presented as an emergency in the provided evidence, but obsolete FFmpeg components create operational risk.

Technical view

CVE-2014-125012 is mapped to CWE-192 and affects FFmpeg 2.0. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L, indicating remotely reachable, low-complexity triggering with limited availability impact only. The specific vulnerable function is not identified in the source bundle.

Likely exposure

Exposure is most likely in applications, pipelines, or services still using FFmpeg 2.0 to parse media from remote or untrusted sources. Systems on newer or vendor-maintained FFmpeg builds may not be affected, but version verification is required.

Exploitation context

The CVE record says remote attack is possible, but the bundle does not show CISA KEV listing, public exploitation evidence, or weaponized details. Treat this as plausible input-triggered denial of service risk, not proven active exploitation.

Researcher notes

The public metadata is sparse: affected function is unknown, impact is limited to availability, and no exploitation evidence is provided. Avoid assuming code execution or broader product impact without local analysis of FFmpeg 2.0 and the referenced patch.

Mitigation direction

  • Identify all FFmpeg deployments and embedded FFmpeg libraries.
  • Replace FFmpeg 2.0 or apply the referenced upstream patch.
  • Prioritize internet-facing or automated media-processing systems.
  • Check vendor or distribution advisories for supported fixed packages.
  • Restrict untrusted media processing until patched, where operationally feasible.

Validation and detection

  • Confirm whether FFmpeg 2.0 is present in production or containers.
  • Check whether libavcodec/dxtroy.c exists in the deployed source build.
  • Verify the referenced upstream commit is included or superseded.
  • Review media ingestion services that accept remote or user-supplied files.
  • Run existing regression tests after updating FFmpeg packages.
Prepared
Confidence
medium
Sources
4

Based on public source material and reviewed before publication.

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.

cwe · low confidence lookup

CWE-192: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2014-125012 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
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2014-125012Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
unspecifiedFFmpeg2.0Listed
Weakness

CWE details

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

CWE-192 · source CWE mapping

Integer Coercion Error

Integer Coercion Error represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.