Bug 1549707 – CVE-2017-18201 libcdio: Double free in get_cdtext_generic() in lib/driver/_cdio_generic.c

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1549707 - (CVE-2017-18201) CVE-2017-18201 libcdio: Double free in get_cdtext_generic() in lib/driver/_cdio_generic.c

Summary:	CVE-2017-18201 libcdio: Double free in get_cdtext_generic() in lib/driver/_cd...

Status:	NEW

Aliases:	CVE-2017-18201

Product:	Security Response
Classification:	Other
Component:	vulnerability (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	low Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Red Hat Product Security
QA Contact:
Docs Contact:

URL:
Whiteboard:	impact=low,public=20180227,reported=2...
Keywords:	Security

Depends On:	1549712 1549713 1553621
Blocks:	1549715
	Show dependency tree / graph

Reported:	2018-02-27 12:02 EST by Pedro Sampaio
Modified:	2018-10-30 03:53 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:	libcdio 2.0.0
Doc Type:	If docs needed, set a value
Doc Text:	A double-free flaw was found in the way libcdio handled processing of ISO files. An attacker could potentially use this flaw to crash applications using libcdio by tricking them into processing crafted ISO files.
Story Points:	---
Clone Of:
Environment:
Last Closed:
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2018:3246	None	None	None	2018-10-30 03:53 EDT

Groups: None (edit)

Description Pedro Sampaio 2018-02-27 12:02:02 EST

An issue was discovered in GNU libcdio before 2.0.0. There is a double free in get_cdtext_generic() in lib/driver/_cdio_generic.c.

Upstream patch:

https://git.savannah.gnu.org/cgit/libcdio.git/commit/?id=dec2f876c2d7162da213429bce1a7140cdbdd734

External References:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=887640

Comment 1 Pedro Sampaio 2018-02-27 12:08:59 EST

Created libcdio tracking bugs for this issue:

Affects: fedora-all [bug 1549713]

Comment 6 rocky 2018-03-13 10:59:39 EDT

I am trying to understand the this bug tracking system. 

When I read:

> Affects: fedora-all [bug 1549713]

What does "fedora-all" mean? As noted previously, the bug was introduced sometime after 0.90 (definitely in 0.94) but fixed in 2.0.0

Comment 7 Adrian Reber 2018-03-13 11:02:20 EDT

I understand 'fedora-all' as all active releases. Currently that would be F26 and F27 with libcdio-0.94 and F-28 and rawhide with libcdio-2.0.0

I patched libcdio for F26 and F27. F28 and rawhide should be on the safe side with 2.0.0.

Comment 8 rocky 2018-03-13 11:12:42 EDT

Thanks for the clarification. So I gather rawhide is not considered to be in "fedora-all"?

Not a big deal. I'm just trying to understand these things in detail and wondering about how accurate such trackers are. Since I happen to know what's up with this one, I'm can it as a gauge for other bug reports where I really have no idea.

Comment 9 rocky 2018-03-13 11:14:09 EDT

I'm can it -> I can use it

Comment 10 errata-xmlrpc 2018-10-30 03:53:07 EDT

This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2018:3246 https://access.redhat.com/errata/RHSA-2018:3246

Note You need to log in before you can comment on or make changes to this bug.