Bug 1185268

Summary: vorbis-tools: division by zero in oggenc / opusenc
Product: [Other] Security Response Reporter: Vasyl Kaigorodov <vkaigoro>
Component: vulnerabilityAssignee: Red Hat Product Security <security-response-team>
Status: CLOSED DUPLICATE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: hdegoede, kdudka, vkaigoro
Target Milestone: ---Keywords: Security
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-23 11:24:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1184452, 1185274    
Bug Blocks: 1185273    
Attachments:
Description Flags
crash_div_zero.wav none

Description Vasyl Kaigorodov 2015-01-23 10:54:46 UTC
It was reported [1] that a crafted WAV file with number of channels set to 0 will cause oggenc and opusenc to crash due to a division by zero issue at :

Stopped reason: SIGFPE 0x0804d497 in wav_open (in=0x805c368, opt=0xbffff2ec, oldbuf=0x805c4d0 "RIFF\f\002", buflen=0xc) at audio.c:552 552 opt->total_samples_per_channel = len/(format.channels*samplesize);

The upstream patches are most likely these:
https://trac.xiph.org/changeset/19423/
https://trac.xiph.org/changeset/19422/

[1]: https://trac.xiph.org/ticket/2137

Comment 1 Vasyl Kaigorodov 2015-01-23 11:02:14 UTC
Created attachment 983301 [details]
crash_div_zero.wav

Comment 2 Kamil Dudka 2015-01-23 11:06:57 UTC
Is this a duplicate of bug #11184448?

Comment 3 Kamil Dudka 2015-01-23 11:07:46 UTC
I meant bug #1184448.

Comment 4 Vasyl Kaigorodov 2015-01-23 11:08:34 UTC
Created vorbis-tools tracking bugs for this issue:

Affects: fedora-all [bug 1185274]

Comment 5 Vasyl Kaigorodov 2015-01-23 11:24:48 UTC
(In reply to Kamil Dudka from comment #3)
> I meant bug #1184448.

This one too. My fault - did not check if these were filed already or not.
Sorry again.

*** This bug has been marked as a duplicate of bug 1184448 ***