LiveActive security incident?Get immediate response
CVE Record

CVE-2014-8962: Stack-based buffer overflow in stream_decoder.c in libFLAC before 1.3.1 allows remote attackers to execute...

Stack-based buffer overflow in stream_decoder.c in libFLAC before 1.3.1 allows remote attackers to execute arbitrary code via a crafted .flac file.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's Takehigh

Analyst readout for executives and security teams

Plain-English summary

CVE-2014-8962 is a memory corruption flaw in libFLAC before 1.3.1. A malicious FLAC audio file could trigger arbitrary code execution when parsed. Business risk is highest where systems automatically ingest or transcode user-supplied audio.

Executive priority

Prioritize remediation where untrusted audio files are processed automatically or at scale. Internet-facing upload, conversion, or media-processing workflows should be handled first. Systems that never parse FLAC files have lower urgency.

Technical view

The CVE describes a stack-based buffer overflow in stream_decoder.c in libFLAC before 1.3.1. The attack vector is a crafted .flac file. The source bundle names upstream and multiple vendor advisories, but provides no CVSS score or CWE metadata.

Likely exposure

Exposure is likely on hosts, applications, or appliances using libFLAC before 1.3.1, including bundled copies. Risk depends on whether untrusted FLAC files are accepted, scanned, previewed, decoded, or transcoded.

Exploitation context

Packet Storm is listed with a code-execution reference, indicating public exploit material existed. The bundle does not show CISA KEV listing or active exploitation evidence, so active exploitation should not be asserted.

Researcher notes

The bundle supports code execution via crafted FLAC input and identifies libFLAC before 1.3.1. It does not provide CVSS metrics, detailed affected downstream products, or confirmed exploitation in the wild. Validate exposure by dependency and runtime use, not package presence alone.

Mitigation direction

  • Upgrade libFLAC to 1.3.1 or a vendor-patched package.
  • Apply relevant OS vendor advisories for maintained distributions.
  • Inventory applications that bundle their own libFLAC copy.
  • Restrict processing of untrusted .flac files until patched.
  • Check vendor guidance for legacy or embedded products.

Validation and detection

  • Identify installed libFLAC package versions across managed assets.
  • Check application dependency manifests for bundled libFLAC before 1.3.1.
  • Confirm media ingestion paths reject or isolate untrusted FLAC files.
  • Verify patched builds are deployed after package updates.
  • Review EDR or application logs for crashes during FLAC parsing.
Prepared
Confidence
medium
Sources
8

Public sources used

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.

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-2014-8962 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
14Source 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.