Description: There exists a denial of service problem in libxml's UTF-8 decoding functions. The xmlCurrentChar() function does not check UTF-8 correctness and certain multibyte combinations can cause the library to enter an infinite loop and hang, consuming system resources. It is strongly recommended to upgrade if your application accepts arbitrary xml user input. Provided by: The issue was originally discovered at Google by Brad Fitzpatrick and further investigated by Peter Valchev and Will Drewry. Patch and debugging by Daniel Veillard (libxml). Acknowledgements: Red Hat would like to thank the Google Security Team for responsibly disclosing this issue.
Created attachment 289757 [details] Upstream patch written by Daniel Veillard
Note that I had to hange the patch slightly on RHEL-2.1 and RHEL-3 due to small differences in code and the lack of availability of an error reporting routine. Oh and I'm the upstream maintainer too if that can be of importance. Daniel
(In reply to comment #4) > Oh and I'm the upstream maintainer too if that can be of importance. I'm aware of it Daniel, and I'm aware that you have written the patch, it's also mentioned in the initial description of this bug. Your patch was explicitly added to the bug to make sure all relevant information is available here for anyone searching for relevant information.
Public now, lifting embargo: http://mail.gnome.org/archives/xml/2008-January/msg00036.html
libxml2-2.6.31-1.fc8 has been pushed to the Fedora 8 stable repository. If problems still persist, please make note of it in this bug report.
libxml2-2.6.31-1.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.
This issue was addressed in: Red Hat Enterprise Linux: http://rhn.redhat.com/errata/RHSA-2008-0032.html Fedora: https://admin.fedoraproject.org/updates/F7/FEDORA-2008-0477 https://admin.fedoraproject.org/updates/F8/FEDORA-2008-0462