If the bdf parser failed to parse the data for the bitmap for any character, it would proceed with an invalid pointer to the bitmap data and later crash when trying to read the bitmap from that pointer. A local user could exploit this issue to crash the X.Org server. Upstream patch: http://cgit.freedesktop.org/xorg/lib/libXfont/commit/?id=78c2e3d70d29698244f70164428bd2868c0ab34c External References: http://www.x.org/wiki/Development/Security/Advisory-2015-03-17/
Created libXfont tracking bugs for this issue: Affects: fedora-all [bug 1203720]
libXfont-1.5.1-1.fc21 has been pushed to the Fedora 21 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 7 Red Hat Enterprise Linux 6 Via RHSA-2015:1708 https://rhn.redhat.com/errata/RHSA-2015-1708.html
Hi guys, Does this problem CVE affect libXfont shipped with RHEL5? Best regards, Dapeng
Dapeng, Yes, from the whiteboard RHEL 5 is affected: rhel-5/libXfont=affected However, RHEL 5 has entered Production Phase 3 as of January 31, 2014. As per our errata policy: "During the Production 3 Phase, Critical impact Security Advisories (RHSAs) and selected Urgent Priority Bug Fix Advisories (RHBAs) may be released as they become available." Red Hat Enterprise Linux Life Cycle https://access.redhat.com/support/policy/updates/errata#Production_3_Phase This means that Red Hat will not be addressing Low, Moderate, or Important impact CVE's in relation to RHEL 5.
Hi Matt, Thank you for your comment. So there is some possibility that this problem will be fixed in rhel5, right? But we can not guarantee that.
Dapeng, Correct. Likely, this will not be fixed in RHEL 5.