Bug 1173109 - (CVE-2020-14415) VUL-1: CVE-2020-14415: qemu: division by zero in oss_write() in audio/ossaudio.c
(CVE-2020-14415)
VUL-1: CVE-2020-14415: qemu: division by zero in oss_write() in audio/ossaudio.c
Status: RESOLVED FIXED
Classification: Novell Products
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents
unspecified
Other Other
: P4 - Low : Minor
: ---
Assigned To: Security Team bot
Security Team bot
https://smash.suse.de/issue/261789/
CVSSv3.1:SUSE:CVE-2020-14415:5.5:(AV:...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2020-06-18 11:41 UTC by Wolfgang Frisch
Modified: 2021-04-09 14:53 UTC (History)
3 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wolfgang Frisch 2020-06-18 11:41:41 UTC
CVE-2020-14415

A divide-by-zero flaw was found in function oss_write() in audio/ossaudio.c, resulting in a possible crash and denial of service scenario.

Upstream fix:
https://git.qemu.org/?p=qemu.git;a=commit;h=7a4ede0047a8613b0e3b72c9d351038f013dd357

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1848117
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2020-14415
Comment 1 Wolfgang Frisch 2020-06-18 12:40:31 UTC
The bug was introduced by this commit:
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=3ba4066d085f5bdce2c7ac145692a4fd52493d67
>Mon, 23 Sep 2019 12:28:47 +0200
>ossaudio: port to the new audio backend api

Affected:
SUSE:SLE-15-SP2:Update
Comment 2 Bruce Rogers 2020-06-24 20:50:43 UTC
Fix is queued for first SLE15-SP2 maintenance update.
Comment 3 Bruce Rogers 2020-06-26 22:05:04 UTC
Note about this fix's inclusion:
At the time the patch was included in the SLE15-SP2 package (see Mar 12, 2020 mention of audio-oss-fix-buffer-pos-calculation.patch in qemu.changes file), this bug report hadn't been created yet.
The patch was removed, since it is now part of the v4.2.1 stable release.
Comment 4 Bruce Rogers 2021-03-25 15:24:02 UTC
Fixed in all affected code streams. Reassigning bug back to security-team.