[30219] in Kerberos

home help back first fref pref prev next nref lref last post

Re: "Stealing" the credential cache

daemon@ATHENA.MIT.EDU (Ken Hornstein)
Wed Aug 13 14:38:28 2008

Message-Id: <200808131837.m7DIaxTM029740@hedwig.cmf.nrl.navy.mil>
To: kerberos@mit.edu
In-Reply-To: <87iqu4u675.fsf@windlord.stanford.edu> 
Date: Wed, 13 Aug 2008 14:36:59 -0400
From: Ken Hornstein <kenh@cmf.nrl.navy.mil>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: kerberos-bounces@mit.edu

>[...]
>This too only protects against casual attacks, since root can still get
>access to this ticket cache by trying hard enough.

It's all about what you define as "casual".  Just opening files in
/proc will not work; your best bet is to ptrace() one of the existing
processes that has the credential cache descriptor available (or simply
attack via ptrace() the credential manager process itself).  From what
I've seen of existing ptrace()-based attack tools this technique
requires some skill and would involve some work.  I prefer to use the
term "unsophisticated" attacks when describing what this credential
cache protects against.  Kernel keyrings are better, of course, but
they're not available everywhere.

I don't think there is a complete solution if you posit an attacker having
root access to a client workstation.  And that old joke who's punchline
is, "I don't have to run faster than the bear, I just have to run faster
than you," comes to mind.

--Ken
________________________________________________
Kerberos mailing list           Kerberos@mit.edu
https://mailman.mit.edu/mailman/listinfo/kerberos

home help back first fref pref prev next nref lref last post