CVE-2017-17054
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn aubio 0.4.6, a divide-by-zero error exists in the function new_aubio_source_wavread() in source_wavread.c, which may lead to DoS when playing a crafted audio file.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA divide-by-zero vulnerability exists in aubio 0.4.6's WAV audio file parser (source_wavread.c) within the new_aubio_source_wavread() function. When processing a specially crafted WAV file containing manipulated header values (specifically a zero divisor value), the application crashes due to the unhandled division by zero, resulting in denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 0.4.6CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed aubio versionRun 'aubio --version' or 'pkg-config --modversion aubio' to retrieve the installed version. If aubio is a library linked to your application, check the library file (e.g., libaubio.so) or inspect your application's dependencies.Affected if The version returned is exactly 0.4.6
-
Verify WAV file processing capability is in useCheck if your application or workflow uses aubio's WAV reading functionality. Search for code or scripts that call 'new_aubio_source_wavread' or process .wav files using aubio.Affected if Your environment processes WAV audio files through aubio's source_wavread module
-
Confirm the application accepts external WAV inputReview your application configuration to determine if it loads WAV files from untrusted or external sources. Check for file upload features, audio processing pipelines, or CLI tools that accept WAV file paths.Affected if Your application processes WAV files from sources you do not fully control or validate
-
Inspect for input validation on WAV headersExamine any pre-processing or validation logic that runs before aubio processes WAV files. Look for checks on WAV header fields, particularly the sample rate, bit depth, or channel count values that could become divisors.Affected if No validation exists on WAV header values before they are used in arithmetic operations within aubio
You are affected if you have aubio version 0.4.6 installed and your application or workflow uses it to process WAV files, especially from external or untrusted sources, without validating WAV header values beforehand.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate to a patched version of aubio that addresses this vulnerability, or implement input validation to ensure WAV file header values used in division operations are non-zero before processing.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17054 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-17054 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data