Vulnerability Assessment & Network Security Forums
If through a vulnerability assessment, a network security issue is detected for the vulnerability below, applying the appropriate security patches in a timely matter is very important. If you have detected that your system has already been compromised, following CERT's Network Security recovery document will assist with recommended steps for system recovery.
Vulnerability Assessment Details
X.org, XFree86: Integer and stack overflows in libXpm
Detailed Explanation for this Vulnerability Assessment
The remote host is affected by the vulnerability described in GLSA-200409-34
(X.org, XFree86: Integer and stack overflows in libXpm)
Chris Evans has discovered multiple integer and stack overflow
vulnerabilities in the X Pixmap library, libXpm, which is a part of the X
Window System. These overflows can be exploited by the execution of a
malicious XPM file, which can crash applications that are dependent on
A carefully-crafted XPM file could crash applications that are linked
against libXpm, potentially permiting the execution of arbitrary code with
the rights of the user running the application.
There is no known workaround at this time.
All X.org users should upgrade to the latest version:
# emerge sync
# emerge -pv ">=x11-base/xorg-x11-6.7.0-r2"
# emerge ">=x11-base/xorg-x11-6.7.0-r2"
All XFree86 users should upgrade to the latest version:
# emerge sync
# emerge -pv ">=x11-base/xfree-4.3.0-r7"
# emerge ">=x11-base/xfree-4.3.0-r7"
Note: Usage of XFree86 is deprecated on the AMD64, HPPA, IA64, MIPS, PPC
and SPARC architectures: XFree86 users on those architectures should switch
to X.org rather than upgrading XFree86.
Network Security Threat Level: Medium
Networks Security ID:
Vulnerability Assessment Copyright: (C) 2005 Michel Arboi
|HP ML350p G8 Tower 12-Core Server 2x E5-2630 2.3GHz 192GB-8 8x 146GB 15K SAS RPS
|HP DL380p G8 16-Core Server 2x E5-2660 2.2GHz 128GB-16 4x 600GB SAS SFF RPS
|HP DL360 G9 12-Core Server 2x E5-2620 v3 2.4GHz 768GB-32 8x 900GB SAS P440ar
No Discussions have been posted on this vulnerability.