CVE-2018-14045
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 · uneditedThe FIRFilter::evaluateFilterMulti function in FIRFilter.cpp in libSoundTouch.a in Olli Parviainen SoundTouch 2.0 allows remote attackers to cause a denial of service (assertion failure and application exit), as demonstrated by SoundStretch.
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 · high confidenceA denial-of-service vulnerability exists in the FIRFilter::evaluateFilterMulti function in libSoundTouch.a (SoundTouch 2.0). Remote attackers can trigger an assertion failure by providing specially crafted audio input processed by SoundStretch or any application using the library, causing the application to exit abruptly.
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= 2.0.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 SoundTouch library presenceSearch for libSoundTouch.a, libSoundTouch.so, or SoundTouch.dll in your system or application dependencies. Check if SoundStretch binary exists on the system.Affected if The SoundTouch library version 2.0.0 is present in the environment
-
Determine exact SoundTouch versionRun 'soundstretch -help' or check the library binary metadata. If building from source, examine the version.h or configure.ac file. Compare against the affected version 2.0.0.Affected if The installed version is exactly 2.0.0 or falls within the affected range
-
Identify applications using SoundTouch librarySearch project dependencies or installed binaries that link against libSoundTouch. Look for audio processing applications, media converters, or any software that performs tempo/pitch adjustment.Affected if An application using SoundTouch library processes external audio input
-
Verify audio input processing pathsReview logs or instrumentation to confirm whether the FIRFilter::evaluateFilterMulti code path is exercised during audio processing operations.Affected if The application processes audio through the evaluateFilterMulti function with untrusted input
Environment is affected if SoundTouch library version 2.0.0 is present AND any application using the library processes external audio input through the vulnerable evaluateFilterMulti function.
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 SoundTouch library to a patched version if available, or implement proper input validation in the evaluateFilterMulti function to prevent the assertion failure condition from being triggered by malicious audio data.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14045 — 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-2018-14045 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