All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom <tom@lemuria.org>
To: SELinux@tycho.nsa.gov
Subject: Re: Do you trust X server?
Date: Fri, 18 Mar 2005 09:35:12 +0100	[thread overview]
Message-ID: <20050318093512.E5491@lemuria.org> (raw)
In-Reply-To: <200503180526.j2I5Q5OP012774@turing-police.cc.vt.edu>; from Valdis.Kletnieks@vt.edu on Fri, Mar 18, 2005 at 12:26:04AM -0500

On Fri, Mar 18, 2005 at 12:26:04AM -0500, Valdis.Kletnieks@vt.edu wrote:
> For a remote exploit of the X server itself, you'd have to find a way to
> exploit the X protocol, 

Not true.

This was 2002, and it was a DoS, but it shows that the X server can be
attacked through remote applications:

http://web.lemuria.org/security/mozilla-dos.html

The short: A font-rendering bug in X can cause a system freeze if mozilla
is instructed to render a huge (like 1666666 pixels) font.


Don't trust X. Microsoft made the mistake of trusting the GUI system,
and we all know what shatter attacks are, don't we?


-- 
http://web.lemuria.org/pubkey.html
pub  1024D/2D7A04F5 2002-05-16 Tom Vogt <tom@lemuria.org>
     Key fingerprint = C731 64D1 4BCF 4C20 48A4  29B2 BF01 9FA1 2D7A 04F5

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2005-03-18  8:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17 22:28 Do you trust X server? Jun OKAJIMA
2005-03-18  5:26 ` Valdis.Kletnieks
2005-03-18  8:35   ` Tom [this message]
2005-03-18 16:58     ` Valdis.Kletnieks
2005-03-18 12:38 ` Stephen Smalley
2005-03-18 16:07   ` Daniel J Walsh
  -- strict thread matches above, loose matches on Subject: below --
2005-03-18 16:21 Casey Schaufler
2005-03-24 20:26 ` Tom
2005-03-24 20:41 Casey Schaufler
2005-03-24 21:02 ` Tom

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050318093512.E5491@lemuria.org \
    --to=tom@lemuria.org \
    --cc=SELinux@tycho.nsa.gov \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.