LiveActive security incident?Get immediate response
CVE Record

CVE-2018-10537: An issue was discovered in WavPack 5.1.0 and earlier.

An issue was discovered in WavPack 5.1.0 and earlier. The W64 parser component contains a vulnerability that allows writing to memory because ParseWave64HeaderConfig in wave64.c does not reject multiple format chunks.

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

Security readout for executives and security teams

Plain-English summary

WavPack 5.1.0 and earlier can mishandle certain Wave64/W64 audio file headers. A malformed file with repeated format chunks may cause unsafe memory writes while being parsed. Treat this as a media-processing risk where vulnerable systems ingest or scan untrusted audio files.

Executive priority

Handle through normal vulnerability management unless WavPack processes untrusted uploads or external media. In those environments, prioritize patch validation because parser memory-write flaws can affect service stability and potentially process integrity.

Technical view

CVE-2018-10537 affects the WavPack W64 parser. ParseWave64HeaderConfig in wave64.c fails to reject multiple format chunks, allowing memory writes during header parsing. The bundle provides no CVSS, CWE, or confirmed active exploitation evidence.

Likely exposure

Exposure is most likely on systems running WavPack 5.1.0 or earlier, including Linux distributions shipping vulnerable wavpack packages, especially where untrusted W64 audio files are processed.

Exploitation context

The source bundle does not show KEV listing or active exploitation. Plausible risk depends on a vulnerable parser opening a crafted W64 file; the bundle does not support claims about remote exploitation or weaponized attacks.

Researcher notes

Focus review on wave64.c header parsing and duplicate format chunk handling. The provided record identifies the vulnerable function and upstream commit, but lacks CVSS, CWE, and exploit-status detail.

Mitigation direction

  • Inventory WavPack versions and distro wavpack packages.
  • Apply relevant Debian, Ubuntu, Fedora, or Slackware security updates.
  • For upstream builds, review WavPack project guidance and the referenced fix commit.
  • Restrict processing of untrusted W64 files until patched.
  • Prioritize media pipelines, upload handlers, and automated scanners.

Validation and detection

  • Confirm installed WavPack is newer than 5.1.0 or vendor-patched.
  • Check package changelogs against DSA-4197, USN-3637-1, or distro advisories.
  • Verify applications do not bundle an old WavPack library.
  • Review file-ingestion paths for W64 audio parsing exposure.
  • Document any compensating controls for untrusted media handling.
Prepared
Confidence
medium
Sources
8

Public sources used

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-2018-10537 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
10Source 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.