Cloudanix VulnDB

CVE-2015-7747

High · 8.8

CVSS

8.8

EPSS

8.8%

Published

Feb 19, 2020

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

A problem in audio software can let attackers crash programs or take over computers if someone opens a specially made sound file.

Exploitation
Requires User Interaction
Attacker needs
User Interaction
Complexity
Low
Impact
Remote Code Execution
Component
Library
Class
Buffer Overflow
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Buffer overflow in afReadFrames allows memory corruption when parsing specially crafted audio files, enabling denial of service or arbitrary code execution.

Why it matters to the business

Organizations relying on media processing or playback applications face risk of application crashes or full system compromise when users open attacker-supplied audio content, with elevated urgency for environments handling untrusted files despite the vulnerability's age and moderate exploit probability.

How an attack unfolds

An attacker creates a malicious audio file that triggers the overflow in afReadFrames, then delivers it to a target who opens it with an affected application or library, resulting in a crash or potential code execution; no named threat actors or ransomware campaigns are associated.

How to fix it

Upgrade the Audio File Library (libaudiofile) to a version containing the fix for this buffer overflow; where no fixed versions are published, replace the library with a maintained fork or disable processing of untrusted audio files.

How to confirm the fix worked

Verify the installed libaudiofile version against known patched releases, recompile or relink dependent applications, and test with the provided proof-of-concept file to confirm absence of crash or code execution.

Typical attack path

  1. Craft audio file that overflows afReadFrames buffer
  2. Distribute file via email, web download, or shared storage
  3. Victim opens file in vulnerable audio-processing application
  4. Overflow occurs during frame reading, leading to crash or shellcode execution

How to detect it

Review application and system logs for crashes or segmentation faults in processes linked to libaudiofile or audiofile when handling audio files; examine file-handling history for recently opened suspicious audio content.

What your security team should do

  • Inventory all systems and applications using libaudiofile and prioritize upgrades
  • Implement application whitelisting or sandboxing for audio file handling
  • Monitor for new patches from distribution vendors and apply within standard change windows
  • Block or filter untrusted audio attachments at email and web gateways where feasible

The record

Buffer overflow in the afReadFrames function in audiofile (aka libaudiofile and Audio File Library) allows user-assisted remote attackers to cause a denial of service (program crash) or possibly execute arbitrary code via a crafted audio file, as demonstrated by sixteen-stereo-to-eight-mono.c.

Affected packages

Ecosystem Package Introduced Fixed
Debian:11 audiofile 0 0.3.6-3
Debian:12 audiofile 0 0.3.6-3
Debian:13 audiofile 0 0.3.6-3
Debian:14 audiofile 0 0.3.6-3
Mageia:5 audiofile 0 0.3.6-4.1.mga5
SUSE:Linux Enterprise Desktop 12 SP1 audiofile 0 0.3.6-10.1
SUSE:Linux Enterprise Desktop 12 SP2 audiofile 0 0.3.6-10.1
SUSE:Linux Enterprise Server 12 SP1 audiofile 0 0.3.6-10.1
SUSE:Linux Enterprise Server 12 SP2 audiofile 0 0.3.6-10.1
SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 audiofile 0 0.3.6-10.1
SUSE:Linux Enterprise Server for SAP Applications 12 SP1 audiofile 0 0.3.6-10.1
SUSE:Linux Enterprise Server for SAP Applications 12 SP2 audiofile 0 0.3.6-10.1
SUSE:Linux Enterprise Software Development Kit 12 SP1 audiofile 0 0.3.6-10.1
SUSE:Linux Enterprise Software Development Kit 12 SP2 audiofile 0 0.3.6-10.1
Ubuntu:14.04:LTS audiofile 0 0.3.6-2ubuntu0.14.04.1
openSUSE:Tumbleweed audiofile 0 0.3.6-9.5

Related vulnerabilities