CVE-2018-14052
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 · uneditedAn issue has been found in libwav through 2017-04-20. It is a SEGV in the function apply_gain in wav_gain/wav_gain.c.
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 segmentation fault (SEGV) vulnerability exists in the apply_gain function in wav_gain/wav_gain.c of the libwav library through 2017-04-20. The vulnerability causes a crash due to a null pointer dereference or invalid memory access when processing WAV audio files with certain gain parameters, leading to 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<= 2017-04-20CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/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.
-
Locate libwav library installationSearch for libwav library files (libwav.so, libwav.a) in standard system paths such as /usr/lib, /usr/local/lib, or within application directories. Also search for source code directories containing wav_gain/wav_gain.cAffected if libwav library files or source code are found on the system
-
Determine libwav version or dateCheck the library file metadata (modification date, version info) or inspect the source code directory for the last commit date before 2017-04-20. Look for version headers or a CHANGELOG file with datesAffected if The installed version is from on or before 2017-04-20, or no newer version information is found
-
Identify applications using libwavSearch application binaries and scripts for linkage to libwav (ldd on Linux, dependency walker on Windows) or grep source code for #include <wav_gain.h> or calls to apply_gainAffected if Applications dynamically or statically link to libwav and invoke its functions
-
Check for WAV file processing with gain parametersReview application logs, configuration files, or source code to determine if WAV audio files are being processed using the apply_gain function with gain parameter valuesAffected if WAV files with gain parameter values are processed using the apply_gain function from libwav
The environment is affected if libwav version dated on or before 2017-04-20 is installed AND an application processes WAV audio files using the apply_gain function, which can trigger the null pointer dereference.
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 libwav to a version after 2017-04-20 that includes the fix for the apply_gain function crash, or apply the vendor patch. Test audio processing functionality thoroughly after the update to ensure the fix doesn't introduce regressions.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-14052 — 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-14052 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