Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 515515 - (CVE-2009-1885) CVE-2009-1885 xerces-c, xerces-c27: Stack overflow when parsing recursive XML structures
CVE-2009-1885 xerces-c, xerces-c27: Stack overflow when parsing recursive XML...
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
low Severity low
: ---
: ---
Assigned To: Red Hat Product Security
http://svn.apache.org/viewvc?view=rev...
impact=low,public=20090805,reported=2...
: Reopened, Security
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-04 11:26 EDT by Jan Lieskovsky
Modified: 2014-12-02 04:13 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2014-11-30 23:10:37 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jan Lieskovsky 2009-08-04 11:26:39 EDT
A stack overflow flaw was found in Apache Xerces by parsing root XML document
element DTD definition. Providing a specially-crafted XML file would
lead to excessive stack growth and denial of service (crash), when
opened by a victim.

Upstream patch:
---------------
http://svn.apache.org/viewvc/xerces/c/trunk/src/xercesc/validators/DTD/DTDScanner.cpp?r1=781488&r2=781487&pathrev=781488&view=patch

Credit:
-------
The flaw was discovered by Jukka Taimisto and Rauli Kaksonen from the
CROSS project at Codenomicon Ltd.
Comment 2 Jan Lieskovsky 2009-08-04 11:51:33 EDT
This issue affects the versions of the xerces-c and xerces-c27 packages,
as shipped with Fedora releases of 10 and 11.

This issue affects the versions of the xerces-c package,
as shipped within the Extra Packages for Enterprise Linux 4 (EPEL-4)
and Extra Packages for Enterprise Linux 5 (EPEL-5) projects.

Please fix.
Comment 4 Jan Lieskovsky 2009-08-06 08:01:50 EDT
Public now via:

    http://www.cert.fi/en/reports/2009/vulnerability2009085.html
Comment 5 Fedora Update System 2009-08-06 10:24:46 EDT
xerces-c-2.8.0-5.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/xerces-c-2.8.0-5.fc10
Comment 6 Fedora Update System 2009-08-06 10:24:54 EDT
xerces-c-2.8.0-5.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/xerces-c-2.8.0-5.fc11
Comment 7 Fedora Update System 2009-08-06 10:56:56 EDT
xerces-c27-2.7.0-8.fc11 has been submitted as an update for Fedora 11.
http://admin.fedoraproject.org/updates/xerces-c27-2.7.0-8.fc11
Comment 8 Fedora Update System 2009-08-06 10:57:04 EDT
xerces-c27-2.7.0-8.fc10 has been submitted as an update for Fedora 10.
http://admin.fedoraproject.org/updates/xerces-c27-2.7.0-8.fc10
Comment 9 Fedora Update System 2009-08-06 10:57:12 EDT
xerces-c-2.7.0-8.el4 has been submitted as an update for Fedora EPEL 4.
http://admin.fedoraproject.org/updates/xerces-c-2.7.0-8.el4
Comment 10 Fedora Update System 2009-08-06 10:57:20 EDT
xerces-c-2.7.0-8.el5 has been submitted as an update for Fedora EPEL 5.
http://admin.fedoraproject.org/updates/xerces-c-2.7.0-8.el5
Comment 13 Jan Lieskovsky 2009-08-07 07:52:17 EDT
This issue affects the versions of Xerces-c package, as shipped
with Red Hat Enterprise MRG 1.1 for Red Hat Enterprise Linux 4
and Red Hat Enterprise Linux 5.
Comment 14 Jan Lieskovsky 2009-08-07 07:54:09 EDT
Official statement from Red Hat Security Response Team regarding this issue:
----------------------------------------------------------------------------

The Red Hat Security Response Team has rated this issue as having low security
impact, a future Xerces-c package update may address this flaw in Red Hat
Enterprise MRG 1.1. More information regarding issue severity can be found here:
http://www.redhat.com/security/updates/classification/
Comment 15 Fedora Update System 2009-08-25 00:25:15 EDT
xerces-c27-2.7.0-8.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 16 Fedora Update System 2009-08-25 00:40:45 EDT
xerces-c-2.8.0-5.fc10 has been pushed to the Fedora 10 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 17 Fedora Update System 2009-08-25 00:41:05 EDT
xerces-c27-2.7.0-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 18 Fedora Update System 2009-08-25 00:47:29 EDT
xerces-c-2.8.0-5.fc11 has been pushed to the Fedora 11 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 19 Fedora Update System 2009-09-01 16:27:40 EDT
xerces-c-2.7.0-8.el5 has been pushed to the Fedora EPEL 5 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 20 Fedora Update System 2009-09-01 16:27:58 EDT
xerces-c-2.7.0-8.el4 has been pushed to the Fedora EPEL 4 stable repository.  If problems still persist, please make note of it in this bug report.
Comment 21 Peter Lemenkov 2009-09-25 09:20:43 EDT
Should be closed now, I suppose.
Comment 22 Tomas Hoger 2009-09-28 07:44:26 EDT
We actually do want to keep this open for bit longer, as xerces-c is shipped as part of some products, but due to the impact of the flaw itself and impact on particular product, updates are not expected to go out immediately.  So I will re-open, feel free to un-CC yourself, as all you care about is fixed by now.

Thank you!
Comment 23 Peter Lemenkov 2009-09-28 07:59:49 EDT
Ok, understood.
Feel free to do everything you need with this ticket :)
Comment 24 Kurt Seifried 2014-11-30 23:10:37 EST
Statement:

Red Hat Product Security has rated this issue as having Low security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.

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