LiveActive security incident?Get immediate response
CVE Record

CVE-2015-8365: The smka_decode_frame function in libavcodec/smacker.c in FFmpeg before 2.6.5, 2.7.x before 2.7.3, and 2.8....

The smka_decode_frame function in libavcodec/smacker.c in FFmpeg before 2.6.5, 2.7.x before 2.7.3, and 2.8.x through 2.8.2 does not verify that the data size is consistent with the number of channels, which allows remote attackers to cause a denial of service (out-of-bounds array access) or possibly have unspecified other impact via crafted Smacker data.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

A flaw in FFmpeg's Smacker audio decoder can let crafted Smacker media crash software using vulnerable FFmpeg builds. The public record frames denial of service as the clear impact, with unspecified other impact only as a possibility. No source in the bundle reports active exploitation. Exposure is most likely where applications, services, or desktop systems process untrusted media through vulnerable FFmpeg versions, especially uploaded or externally supplied Smacker files. The source bundle does not identify specific downstream products beyond FFmpeg and distribution packages. Handle through normal vulnerability remediation unless the organization processes untrusted media at scale. Prioritize public-facing upload pipelines, content moderation systems, and media conversion services because a crash can affect availability. Mitigation focus: Upgrade FFmpeg to 2.6.5, 2.7.3, 2.8.3, or later supported vendor packages.; Apply relevant distribution security updates from Ubuntu, openSUSE, or Debian where applicable.; Check vendor guidance for downstream products embedding or bundling FFmpeg..

Prepared

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-2015-8365 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
1Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

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.