LiveActive security incident?Get immediate response
CVE Record

CVE-2022-33064: An off-by-one error in function wav_read_header in src/wav.c in Libsndfile 1.1.0, results in a write out of...

An off-by-one error in function wav_read_header in src/wav.c in Libsndfile 1.1.0, results in a write out of bound, which allows an attacker to execute arbitrary code, Denial of Service or other unspecified impacts.

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

Security readout for executives and security teams

Plain-English summary

This CVE describes a memory write bug in Libsndfile 1.1.0 when reading WAV headers. If an exposed application processes attacker-supplied audio files with this library, impacts may include crashes, arbitrary code execution, or other unspecified effects. Public sources do not provide CVSS scoring or confirmed exploitation.

Executive priority

Treat this as a targeted dependency exposure review, not a confirmed emergency. Priority should rise if customer-facing or partner-facing systems process WAV files using Libsndfile 1.1.0, because the reported impact includes code execution and service disruption.

Technical view

CVE-2022-33064 is reported as an off-by-one error in wav_read_header in src/wav.c in Libsndfile 1.1.0, causing an out-of-bounds write. The CVE text claims possible arbitrary code execution, denial of service, or unspecified impacts, but the provided sources do not include exploit status, CVSS metrics, or a named fixed version.

Likely exposure

Exposure is most likely in applications, services, or batch pipelines that use Libsndfile 1.1.0 to parse WAV files from users, partners, email, web uploads, or other untrusted sources. The source bundle does not identify downstream products or package ecosystems.

Exploitation context

The source bundle does not show CISA KEV listing or another cited source confirming active exploitation. The GitHub issue is public, so defenders should assume technical details may be discoverable, but avoid treating exploitation as confirmed from these sources alone.

Researcher notes

Evidence is thin: the CVE record names the vulnerable function and version, but no CVSS, CWE, fixed release, affected CPEs, or exploitation confirmation are present in the bundle. Validation should focus on dependency discovery and reachable untrusted WAV parsing paths.

Mitigation direction

  • Inventory where Libsndfile 1.1.0 is used in production and build artifacts.
  • Check Libsndfile maintainer guidance and release notes for a fixed version.
  • Prioritize systems that parse WAV files from untrusted or external users.
  • Temporarily restrict untrusted WAV processing where business impact allows.
  • Run audio parsing workloads with least privilege and isolation.

Validation and detection

  • Confirm installed Libsndfile versions across hosts, containers, and dependencies.
  • Map which applications pass WAV input into Libsndfile.
  • Review crash telemetry for WAV parsing failures or memory corruption signals.
  • Check whether public upload, API, or email workflows accept WAV files.
  • Verify remediation against vendor guidance once a fixed version is identified.
Prepared
Confidence
medium
Sources
3

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.

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-2022-33064 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
2Source 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.