Debian LinuxOperating system · Debian
CVE-2017-14160
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 bark_noise_hybridmp function in psy.c in Xiph.Org libvorbis 1.3.5 allows remote attackers to cause a denial of service (out-of-bounds access and application crash) or possibly have unspecified other impact via a crafted mp4 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 · high confidenceA buffer over-read vulnerability exists in the bark_noise_hybridmp function in psy.c of Xiph.Org libvorbis 1.3.5. When processing a specially crafted MP4 file, the function accesses memory outside the allocated buffer bounds, leading to denial of service via application crash and potentially allowing arbitrary code execution.
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
Debian LinuxOperating system
= 8.0= 9.0= 1.3.5CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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.
-
Check installed libvorbis package versionRun 'dpkg -l | grep libvorbis' on Debian-based systems, or 'rpm -qa | grep vorbis' on RHEL-based systems, to list installed vorbis packages and their versionsAffected if The installed version is 1.3.5 exactly, indicating the vulnerable version is present
-
Locate libvorbis shared library and query its versionRun 'ldconfig -p | grep vorbis' to find the libvorbis library path, then use 'strings <path> | grep -i version' or check the file metadata to determine the library versionAffected if The library file resolves to version 1.3.5 or the version cannot be determined but is known to be older than 1.3.6
-
Identify applications linking to libvorbisRun 'ldd <application_binary> | grep vorbis' or 'ldconfig -p | grep vorbis' to see which programs load the libvorbis library at runtimeAffected if Any application that processes audio is loading libvorbis and the version is 1.3.5
-
Determine if MP4 audio processing uses libvorbisReview application documentation or run 'strings <application> | grep -i vorbis' to confirm whether the software uses libvorbis to decode MP4 audio filesAffected if The application uses libvorbis to handle MP4 audio and the library version is 1.3.5
A system is affected if libvorbis version 1.3.5 is installed and any application uses it to process MP4 audio files, which can trigger the buffer over-read in bark_noise_hybridmp.
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 libvorbis to version 1.3.6 or later, which contains the patch for this vulnerability. If immediate patching is not possible, validate all MP4 audio input through libvorbis before processing and consider implementing input length checks.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14160 — 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-14160 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