ID CVE-2008-1142
Summary rxvt 2.6.4 opens a terminal window on :0 if the DISPLAY environment variable is not set, which might allow local users to hijack X11 connections. NOTE: it was later reported that rxvt-unicode, mrxvt, aterm, multi-aterm, and wterm are also affected. NOTE: realistic attack scenarios require that the victim enters a command on the wrong machine.
References
Vulnerable Configurations
  • cpe:2.3:a:rxvt:rxvt:2.6.4
    cpe:2.3:a:rxvt:rxvt:2.6.4
  • cpe:2.3:a:aterm:aterm:1.00:beta4
    cpe:2.3:a:aterm:aterm:1.00:beta4
  • cpe:2.3:a:aterm:aterm:1.00:beta3
    cpe:2.3:a:aterm:aterm:1.00:beta3
  • cpe:2.3:a:aterm:aterm:1.00:beta2
    cpe:2.3:a:aterm:aterm:1.00:beta2
  • cpe:2.3:a:aterm:aterm:1.00:beta1
    cpe:2.3:a:aterm:aterm:1.00:beta1
  • cpe:2.3:a:aterm:aterm:0.4.1
    cpe:2.3:a:aterm:aterm:0.4.1
  • cpe:2.3:a:aterm:aterm:0.4.2
    cpe:2.3:a:aterm:aterm:0.4.2
  • cpe:2.3:a:aterm:aterm:0.4.0
    cpe:2.3:a:aterm:aterm:0.4.0
  • cpe:2.3:a:aterm:aterm:0.3.6
    cpe:2.3:a:aterm:aterm:0.3.6
  • cpe:2.3:a:aterm:aterm:0.3.5
    cpe:2.3:a:aterm:aterm:0.3.5
  • cpe:2.3:a:aterm:aterm:0.3.4
    cpe:2.3:a:aterm:aterm:0.3.4
  • cpe:2.3:a:aterm:aterm:0.3.3
    cpe:2.3:a:aterm:aterm:0.3.3
  • cpe:2.3:a:aterm:aterm:0.3.2
    cpe:2.3:a:aterm:aterm:0.3.2
  • cpe:2.3:a:aterm:aterm:0.3.1
    cpe:2.3:a:aterm:aterm:0.3.1
  • cpe:2.3:a:aterm:aterm:0.3.0
    cpe:2.3:a:aterm:aterm:0.3.0
  • cpe:2.3:a:aterm:aterm:0.1.1
    cpe:2.3:a:aterm:aterm:0.1.1
  • cpe:2.3:a:aterm:aterm:0.2.0
    cpe:2.3:a:aterm:aterm:0.2.0
  • cpe:2.3:a:aterm:aterm:0.1.0
    cpe:2.3:a:aterm:aterm:0.1.0
  • cpe:2.3:a:eterm:eterm:0.9.2
    cpe:2.3:a:eterm:eterm:0.9.2
  • cpe:2.3:a:mrxvt:mrxvt:0.4.2
    cpe:2.3:a:mrxvt:mrxvt:0.4.2
  • cpe:2.3:a:mrxvt:mrxvt:0.5.2
    cpe:2.3:a:mrxvt:mrxvt:0.5.2
  • cpe:2.3:a:eterm:eterm:0.9.3
    cpe:2.3:a:eterm:eterm:0.9.3
  • cpe:2.3:a:aterm:aterm:1.0.0
    cpe:2.3:a:aterm:aterm:1.0.0
  • cpe:2.3:a:multi-aterm:multi-aterm:0.2
    cpe:2.3:a:multi-aterm:multi-aterm:0.2
  • cpe:2.3:a:multi-aterm:multi-aterm:0.1
    cpe:2.3:a:multi-aterm:multi-aterm:0.1
  • cpe:2.3:a:multi-aterm:multi-aterm:0.0.5
    cpe:2.3:a:multi-aterm:multi-aterm:0.0.5
  • cpe:2.3:a:multi-aterm:multi-aterm:0.0.4
    cpe:2.3:a:multi-aterm:multi-aterm:0.0.4
  • cpe:2.3:a:multi-aterm:multi-aterm:0.0.3
    cpe:2.3:a:multi-aterm:multi-aterm:0.0.3
  • cpe:2.3:a:multi-aterm:multi-aterm:0.0.1
    cpe:2.3:a:multi-aterm:multi-aterm:0.0.1
  • cpe:2.3:a:rxvt:rxvt:2.6.3
    cpe:2.3:a:rxvt:rxvt:2.6.3
  • cpe:2.3:a:rxvt:rxvt:2.6.2
    cpe:2.3:a:rxvt:rxvt:2.6.2
  • cpe:2.3:a:rxvt:rxvt:2.6.1
    cpe:2.3:a:rxvt:rxvt:2.6.1
  • cpe:2.3:a:rxvt:rxvt:2.7.5
    cpe:2.3:a:rxvt:rxvt:2.7.5
  • cpe:2.3:a:rxvt:rxvt:2.7.6
    cpe:2.3:a:rxvt:rxvt:2.7.6
  • cpe:2.3:a:rxvt:rxvt:2.7.7
    cpe:2.3:a:rxvt:rxvt:2.7.7
  • cpe:2.3:a:rxvt:rxvt:2.7.8
    cpe:2.3:a:rxvt:rxvt:2.7.8
  • cpe:2.3:a:rxvt:rxvt:2.7.9
    cpe:2.3:a:rxvt:rxvt:2.7.9
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:9.01
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:9.01
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:9.0
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:9.0
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.9
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.9
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.8
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.8
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.7
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.7
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.6
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.6
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.5a
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.5a
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.5
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.5
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.4
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.4
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.3
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.3
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.2
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.2
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.1
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.1
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.0
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:8.0
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.9
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.9
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.8
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.8
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.7
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.7
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.6
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.6
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.5
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.5
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.4
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.4
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.3
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.3
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.2
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.2
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.1
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.1
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.0
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:7.0
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:6.3
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:6.3
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:6.2
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:6.2
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:6.1
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:6.1
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:6.0
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:6.0
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.9
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.9
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.8
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.8
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.7
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.7
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.6
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.6
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.5
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.5
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.4
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.4
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.3
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.3
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.2
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.2
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.1
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.1
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.0
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:5.0
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.9
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.9
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.8
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.8
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.7
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.7
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.6
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.6
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.5
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.5
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.4
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.4
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.3
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.3
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.2
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.2
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.1
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.1
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.0
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:4.0
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.9
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.9
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.8
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.8
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.7
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.7
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.6
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.6
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.5
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.5
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.4
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.4
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.3
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.3
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.2
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.2
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.1
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.1
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.0
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:3.0
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.9
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.9
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.8
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.8
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.7
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.7
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.6
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.6
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.5
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.5
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.4
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.4
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.3
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.3
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.2
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.2
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.1
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.1
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.0
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:2.0
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.91
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.91
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.9
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.9
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.8
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.8
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.7
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.7
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.6
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.6
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.5
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.5
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.4
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.4
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.3
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.3
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.2
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.2
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.1
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.1
  • cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.0
    cpe:2.3:a:rxvt-unicode:rxvt-unicode:1.0
  • cpe:2.3:a:wterm:wterm:6.2.8a2
    cpe:2.3:a:wterm:wterm:6.2.8a2
  • cpe:2.3:a:wterm:wterm:6.2.6
    cpe:2.3:a:wterm:wterm:6.2.6
  • cpe:2.3:a:wterm:wterm:6.2.5
    cpe:2.3:a:wterm:wterm:6.2.5
CVSS
Base: 3.7 (as of 08-04-2008 - 09:32)
Impact:
Exploitability:
CWE CWE-264
CAPEC
  • Accessing, Modifying or Executing Executable Files
    An attack of this type exploits a system's configuration that allows an attacker to either directly access an executable file, for example through shell access; or in a possible worst case allows an attacker to upload a file and then execute it. Web servers, ftp servers, and message oriented middleware systems which have many integration points are particularly vulnerable, because both the programmers and the administrators must be in synch regarding the interfaces and the correct privileges for each interface.
  • Leverage Executable Code in Non-Executable Files
    An attack of this type exploits a system's trust in configuration and resource files, when the executable loads the resource (such as an image file or configuration file) the attacker has modified the file to either execute malicious code directly or manipulate the target process (e.g. application server) to execute based on the malicious configuration parameters. Since systems are increasingly interrelated mashing up resources from local and remote sources the possibility of this attack occurring is high. The attack can be directed at a client system, such as causing buffer overrun through loading seemingly benign image files, as in Microsoft Security Bulletin MS04-028 where specially crafted JPEG files could cause a buffer overrun once loaded into the browser. Another example targets clients reading pdf files. In this case the attacker simply appends javascript to the end of a legitimate url for a pdf (http://www.gnucitizen.org/blog/danger-danger-danger/) http://path/to/pdf/file.pdf#whatever_name_you_want=javascript:your_code_here The client assumes that they are reading a pdf, but the attacker has modified the resource and loaded executable javascript into the client's browser process. The attack can also target server processes. The attacker edits the resource or configuration file, for example a web.xml file used to configure security permissions for a J2EE app server, adding role name "public" grants all users with the public role the ability to use the administration functionality. The server trusts its configuration file to be correct, but when they are manipulated, the attacker gains full control.
  • Blue Boxing
    This type of attack against older telephone switches and trunks has been around for decades. A tone is sent by an adversary to impersonate a supervisor signal which has the effect of rerouting or usurping command of the line. While the US infrastructure proper may not contain widespread vulnerabilities to this type of attack, many companies are connected globally through call centers and business process outsourcing. These international systems may be operated in countries which have not upgraded Telco infrastructure and so are vulnerable to Blue boxing. Blue boxing is a result of failure on the part of the system to enforce strong authorization for administrative functions. While the infrastructure is different than standard current applications like web applications, there are historical lessons to be learned to upgrade the access control for administrative functions.
  • Restful Privilege Elevation
    Rest uses standard HTTP (Get, Put, Delete) style permissions methods, but these are not necessarily correlated generally with back end programs. Strict interpretation of HTTP get methods means that these HTTP Get services should not be used to delete information on the server, but there is no access control mechanism to back up this logic. This means that unless the services are properly ACL'd and the application's service implementation are following these guidelines then an HTTP request can easily execute a delete or update on the server side. The attacker identifies a HTTP Get URL such as http://victimsite/updateOrder, which calls out to a program to update orders on a database or other resource. The URL is not idempotent so the request can be submitted multiple times by the attacker, additionally, the attacker may be able to exploit the URL published as a Get method that actually performs updates (instead of merely retrieving data). This may result in malicious or inadvertent altering of data on the server.
  • Target Programs with Elevated Privileges
    This attack targets programs running with elevated privileges. The attacker would try to leverage a bug in the running program and get arbitrary code to execute with elevated privileges. For instance an attacker would look for programs that write to the system directories or registry keys (such as HKLM, which stores a number of critical Windows environment variables). These programs are typically running with elevated privileges and have usually not been designed with security in mind. Such programs are excellent exploit targets because they yield lots of power when they break. The malicious user try to execute its code at the same level as a privileged system call.
  • Manipulating Input to File System Calls
    An attacker manipulates inputs to the target software which the target software passes to file system calls in the OS. The goal is to gain access to, and perhaps modify, areas of the file system that the target software did not intend to be accessible.
Access
VectorComplexityAuthentication
LOCAL HIGH NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL PARTIAL
nessus via4
  • NASL family SuSE Local Security Checks
    NASL id SUSE_11_0_RXVT-UNICODE-080814.NASL
    description It was possible to open a terminal on :0 when the environment variable was not set. This could be exploited by local users to hijack X11 connections (CVE-2008-1142).
    last seen 2019-02-21
    modified 2014-06-13
    plugin id 40125
    published 2009-07-21
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=40125
    title openSUSE Security Update : rxvt-unicode (rxvt-unicode-163)
  • NASL family Mandriva Local Security Checks
    NASL id MANDRIVA_MDVSA-2008-161.NASL
    description A vulnerability in rxvt allowed it to open a terminal on :0 if the environment variable was not set, which could be used by a local user to hijack X11 connections (CVE-2008-1142). The updated packages have been patched to correct this issue.
    last seen 2019-02-21
    modified 2018-07-19
    plugin id 36624
    published 2009-04-23
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=36624
    title Mandriva Linux Security Advisory : rxvt (MDVSA-2008:161)
  • NASL family SuSE Local Security Checks
    NASL id SUSE_RXVT-UNICODE-5541.NASL
    description It was possible to open a terminal on :0 when the environment variable was not set. This could be exploited by local users to hijack X11 connections (CVE-2008-1142).
    last seen 2019-02-21
    modified 2014-06-13
    plugin id 34042
    published 2008-08-24
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=34042
    title openSUSE 10 Security Update : rxvt-unicode (rxvt-unicode-5541)
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-200805-03.NASL
    description The remote host is affected by the vulnerability described in GLSA-200805-03 (Multiple X11 terminals: Local privilege escalation) Bernhard R. Link discovered that RXVT opens a terminal on :0 if the '-display' option is not specified and the DISPLAY environment variable is not set. Further research by the Gentoo Security Team has shown that aterm, Eterm, Mrxvt, multi-aterm, rxvt-unicode, and wterm are also affected. Impact : A local attacker could exploit this vulnerability to hijack X11 terminals of other users. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-08-10
    plugin id 32151
    published 2008-05-09
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=32151
    title GLSA-200805-03 : Multiple X11 terminals: Local privilege escalation
refmap via4
bid 28512
confirm http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=469296
gentoo GLSA-200805-03
mandriva
  • MDVSA-2008:161
  • MDVSA-2008:221
misc http://article.gmane.org/gmane.comp.security.oss.general/122
secunia
  • 29576
  • 30224
  • 30225
  • 30226
  • 30227
  • 30229
  • 31687
suse SUSE-SR:2008:017
statements via4
contributor Joshua Bressers
lastmodified 2008-04-14
organization Red Hat
statement Red Hat is aware of this issue and is tracking it via the following bug: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=CVE-2008-1142 This issue does not affect Red Hat Enterprise Linux 3, 4, or 5. The Red Hat Security Response Team has rated this issue as having low security impact. Due to the minimal security consequences of this issue, we do not intend to fix this in Red Hat Enterprise Linux 2.1. More information regarding issue severity can be found here: http://www.redhat.com/security/updates/classification/
Last major update 26-02-2009 - 00:00
Published 07-04-2008 - 13:44
Back to Top