When parsing replies received from the font server, these calls do not check that their calculations for how much memory is needed to handle the returned data have not overflowed, so can result in allocating too little memory and then writing the returned data past the end of the allocated buffer. Affected functions: fs_get_reply(), fs_alloc_glyphs(), fs_read_extent_info() Acknowledgements: Red Hat would like to thank the X.org project for reporting this issue. Upstream acknowledges Ilja van Sprundel as the original reporter of this issue.
Upstream commits: http://cgit.freedesktop.org/xorg/lib/libXfont/commit/?id=a42f707f8a62973f5e8bbcd08afb10a79e9cee33 http://cgit.freedesktop.org/xorg/lib/libXfont/commit/?id=c578408c1fd4db09e4e3173f8a9e65c81cc187c1 http://cgit.freedesktop.org/xorg/lib/libXfont/commit/?id=0f1a5d372c143f91a602bdf10c917d7eabaee09b External Reference: http://lists.x.org/archives/xorg-announce/2014-May/002431.html
Created libXfont tracking bugs for this issue: Affects: fedora-all [bug 1097397]
Statement: (none)
libXfont-1.4.8-1.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
libXfont-1.4.8-1.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
This issue has been addressed in the following products: Red Hat Enterprise Linux 6 Red Hat Enterprise Linux 7 Via RHSA-2014:1870 https://rhn.redhat.com/errata/RHSA-2014-1870.html
IssueDescription: Multiple out-of-bounds write flaws were found in the way libXfont parsed replies received from an X.org font server. A malicious X.org server could cause an X client to crash or, possibly, execute arbitrary code with the privileges of the X.Org server.
This issue has been addressed in the following products: Red Hat Enterprise Linux 5 Via RHSA-2014:1893 https://rhn.redhat.com/errata/RHSA-2014-1893.html