CVE-2011-3937: n/a vulnerability

CVE-2011-3937: The H.263 codec (libavcodec/h263dec.c) in FFmpeg 0.7.x before 0.7.12, 0.8.x before 0.8.11, and unspecified...

The H.263 codec (libavcodec/h263dec.c) in FFmpeg 0.7.x before 0.7.12, 0.8.x before 0.8.11, and unspecified versions before 0.10, and in Libav 0.5.x before 0.5.9, 0.6.x before 0.6.6, 0.7.x before 0.7.5, and 0.8.x before 0.8.1 has unspecified impact and attack vectors related to "width/height changing with frame threads."

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 23:53 UTC (UTC+00:00)

Security readout for executives and security teams

This CVE affects older FFmpeg and Libav media-decoding libraries. The public record does not state a concrete impact, but the issue is tied to H.263 video decoding when frame dimensions change with threaded decoding. Systems that process untrusted video should treat outdated embedded copies as exposure. Exposure is most likely where applications, services, appliances, or pipelines use vulnerable FFmpeg or Libav versions to decode H.263 video, especially from user-supplied media. Bundled or statically linked copies may persist after operating system packages are updated. Prioritize remediation for internet-facing or customer-facing media-processing workflows. For internal systems without untrusted video input, urgency is lower but still worth closing because affected versions are obsolete and may contain other unresolved media parser issues. Mitigation focus: Upgrade FFmpeg 0.7.x to 0.7.12, 0.8.x to 0.8.11, or a non-vulnerable later release.; Upgrade Libav 0.5.x to 0.5.9, 0.6.x to 0.6.6, 0.7.x to 0.7.5, or 0.8.x to 0.8.1.; Replace statically bundled FFmpeg or Libav copies in applications, appliances, and container images..

Prepared: Jun 24, 2026, 12:04 UTC (UTC+00:00)

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-2011-3937 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: Jan 5, 2013, 00:00 UTC (UTC+00:00)

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

1Source links

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

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.