Bug 561457 (CVE-2010-0409)

Summary:	CVE-2010-0409 gmime, gmime22: Buffer overflow by calculating the maximum number of output bytes generated by an uuencode operation
Product:	[Other] Security Response	Reporter:	Jan Lieskovsky <jlieskov>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED ERRATA	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	alexl, bjohnson, lxtnow
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
URL:	http://ftp.gnome.org/pub/GNOME/sources/gmime/2.4/gmime-2.4.15.changes
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-10-19 09:10:15 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:	566838
Bug Blocks:

Description Jan Lieskovsky 2010-02-03 17:26:16 UTC

Buffer overflow flaw was reported and fixed in the GMime library,
in the code part responsible for calculating the maximum number
of output bytes generated by an uuencode operation. 

If a local user was tricked into running a specially-crafted
application, using the library, it could lead to denial of
service (supplied application crash) or, potentially, to arbitrary
code execution with the privileges of the user running that
application.

Upstream v2.4.15 changes file:
  http://ftp.gnome.org/pub/GNOME/sources/gmime/2.4/gmime-2.4.15.changes

Diff between v2.4.14 and v2.4.15:
  http://ftp.gnome.org/pub/GNOME/sources/gmime/2.4/gmime-2.4.14-2.4.15.diff.gz

References:
  http://secunia.com/advisories/38459/
  http://ftp.gnome.org/pub/GNOME/sources/gmime/2.4/gmime-2.4.15.tar.gz

CVE Request:
  http://www.openwall.com/lists/oss-security/2010/02/03/2

Comment 1 Jan Lieskovsky 2010-02-03 17:32:41 UTC

This issue affects the latest versions of the gmime and gmime22 packages,
as shipped with Fedora release of 11 (gmime-2.4.3-6.fc11, 
gmime22-2.2.23-5.fc11) and 12 (gmime-2.4.11-1.fc12, gmime22-2.2.23-7.fc12).

Please fix.

This issue does NOT affect the versions of the gmime package, as 
shipped within Extra Packages for Enterprise Linux -- EPEL-4
(gmime-2.2.1-2.el4) and EPEL-5 (gmime-2.2.3-3.1.el5) projects.

Comment 2 Fedora Update System 2010-02-04 02:27:21 UTC

gmime22-2.2.23-8.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/gmime22-2.2.23-8.fc11

Comment 3 Fedora Update System 2010-02-04 02:28:09 UTC

gmime22-2.2.23-8.fc12 has been submitted as an update for Fedora 12.
http://admin.fedoraproject.org/updates/gmime22-2.2.23-8.fc12

Comment 4 Jan Lieskovsky 2010-02-04 09:05:43 UTC

This is CVE-2010-0409.

Comment 5 Fedora Update System 2010-02-05 01:17:47 UTC

gmime22-2.2.23-8.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 6 Fedora Update System 2010-02-05 01:39:47 UTC

gmime22-2.2.23-8.fc12 has been pushed to the Fedora 12 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 8 Jan Lieskovsky 2010-03-16 10:45:36 UTC

Alex, Xavier, Bernard,

  could you please schedule F11 and F12 gmime updates?
(current gmime-2.4.3-6.fc11 and gmime-2.4.11-1.fc12 are
 still prone to this flaw).

Thanks && Regards, Jan.
--
Jan iankko Lieskovsky / Red Hat Security Response Team