dbcve.org
Debian LinuxOperating system · Debian

CVE-2018-10393

HIGH · 7.5 CVSS v3.1 Published 2018-04-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
bark_noise_hybridmp in psy.c in Xiph.Org libvorbis 1.3.6 has a stack-based buffer over-read.

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 confidence

A stack-based buffer over-read vulnerability exists in the bark_noise_hybridmp function in psy.c of Xiph.Org libvorbis version 1.3.6. An attacker could potentially read sensitive stack memory contents by providing a specially crafted Vorbis audio file to be decoded, leading to information disclosure.

MitigationUpgrade libvorbis to version 1.3.6 or later where the vulnerability has been patched. If upgrading is not immediately feasible, implement input validation on audio files before decoding and consider network-level restrictions on untrusted audio content.

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
Affected:= 8.0= 9.0
Enterprise LinuxOperating system
Affected:= 8.0
Enterprise Linux EusOperating system
Affected:= 8.1= 8.2= 8.4
Enterprise Linux Server AusOperating system
Affected:= 8.2= 8.4
Enterprise Linux Server TusOperating system
Affected:= 8.2= 8.4
LibvorbisApplication
Affected:= 1.3.6

CVSS 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.1/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if libvorbis is installed
    Run 'dpkg -l | grep libvorbis' on Debian-based systems or 'rpm -qa | grep libvorbis' on RHEL-based systems. On Linux systems also check 'ldconfig -p | grep vorbis' to see if the library is loaded.
    Affected if libvorbis is found installed on the system
  2. Determine the installed libvorbis version
    Run 'dpkg -s libvorbis0' or 'rpm -qi libvorbis' to retrieve the exact version number. Alternatively, check the library file directly with 'objdump -p /usr/lib/*/libvorbis.so* | grep SONAME' or check the package metadata.
    Affected if The installed version is exactly 1.3.6
  3. Identify applications using libvorbis for audio decoding
    Search for software that links against libvorbis by running 'ldd /path/to/media/player | grep vorbis' or check application dependencies. Common consumers include FFmpeg, VLC, Audacity, and audio codecs.
    Affected if Any application that decodes Vorbis audio files is present and uses the vulnerable library version
  4. Verify if decoding functionality is accessible
    Test if the system can process Vorbis audio files by attempting to decode a sample .ogg file using tools like 'ffmpeg -i sample.ogg' or 'vorbiscomment sample.ogg'. Check if the decoding path reaches the bark_noise_hybridmp function in psy.c.
    Affected if Vorbis audio decoding is possible and the library version is 1.3.6
  5. Review audio file processing from untrusted sources
    Audit logs or access records for incoming audio files from external or untrusted sources that may have been processed by libvorbis. Check if any automated systems process user-uploaded .ogg files.
    Affected if The system has processed Vorbis files from untrusted sources using the vulnerable library version 1.3.6

A system is affected if libvorbis version 1.3.6 is installed AND any application uses it to decode Vorbis audio files, as the buffer over-read triggers during audio decoding of specially crafted files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade libvorbis to version 1.3.6 or later where the vulnerability has been patched. If upgrading is not immediately feasible, implement input validation on audio files before decoding and consider network-level restrictions on untrusted audio content.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-10393 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-10393 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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