Bug 732335 - Fix various problems and harden the XPath evaluation engine
Summary: Fix various problems and harden the XPath evaluation engine
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: libxml2
Version: 6.2
Hardware: Unspecified
OS: Unspecified
Target Milestone: rc
: ---
Assignee: Daniel Veillard
QA Contact: qe-baseos-tools
Depends On:
Blocks: 747120
TreeView+ depends on / blocked
Reported: 2011-08-22 03:30 UTC by Daniel Veillard
Modified: 2011-12-06 18:55 UTC (History)
2 users (show)

Fixed In Version: libxml2-2.7.6-4.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-12-06 18:55:34 UTC

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2011:1749 normal SHIPPED_LIVE Low: libxml2 security and bug fix update 2011-12-06 01:01:47 UTC

Description Daniel Veillard 2011-08-22 03:30:29 UTC
Description of problem: The version of XPath in RHEL-6.1
has a number of problems which are fixed upstream, like
memory leaks, memory allocation errors and a correctness

Version-Release number of selected component (if applicable):

How reproducible: not very easy

Steps to Reproduce:
Actual results:

Expected results:

Additional info:

Comment 3 RHEL Product and Program Management 2011-08-22 03:47:51 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support

Comment 12 errata-xmlrpc 2011-12-06 18:55:34 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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