RE: Threat vector of running a service using a domain account
- From: "Ramsdell, Scott" <Scott.Ramsdell@xxxxxxxxxxx>
- Date: Fri, 14 Sep 2007 15:34:55 -0400
From recollection, cachedump grabs the hashes that have been stored inthe registry.
It is persistent across reboots therefore, and effected by the "Number
of logons to cache" setting in AD.
I've used cachedump to demonstrate why the Helpdesk shouldn't login to
user's workstations with domain admin creds, when the users themselves
are local admins.
Kind Regards,
Scott Ramsdell
-----Original Message-----
From: Roger A. Grimes [mailto:roger@xxxxxxxxxxxxxx]
Sent: Friday, September 14, 2007 2:25 PM
To: Ramsdell, Scott; Ali, Saqib; Jay
Cc: smanaois3@xxxxxxxxx; security-basics@xxxxxxxxxxxxxxxxx
Subject: RE: Threat vector of running a service using a domain account
I'm not sure...so I'm just spectulating...but
All service account passwords are stored locally in the LSA secrets
store.
Cachedump only works locally against the cached passwords, left in
MEMORY to facilitate service authentications. You can't get to the
truly stored hashes on the disk because they are protected by a secure
mechanism, so you have to get them in the memory cache area. I'm
guessing that the real hash is stored securely. When the service starts
up and uses a Kerberos account, the pre-auth hash is sent, and in memory
briefly. But after the pre-auth handshake, what is kept in memory is the
Kerberos token, which is now used for all future auth. needs for the
next 10 hours or more.
I could, and may be wrong.
Roger
*****************************************************************
*Roger A. Grimes, InfoWorld, Security Columnist
*CPA, CISSP, CISA, MCSE: Security (2000/2003), CEH, yada...yada...
*email: roger_grimes@xxxxxxxxxxxxx or roger@xxxxxxxxxxxxxx
*Author of Windows Vista Security: Securing Vista Against Malicious
Attacks (Wiley)
*http://www.amazon.com/Windows-Vista-Security-Securing-Malicious/dp/0470
101555
*****************************************************************
-----Original Message-----
From: listbounce@xxxxxxxxxxxxxxxxx [mailto:listbounce@xxxxxxxxxxxxxxxxx]
On Behalf Of Ramsdell, Scott
Sent: Friday, September 14, 2007 9:01 AM
To: Ali, Saqib; Jay
Cc: smanaois3@xxxxxxxxx; security-basics@xxxxxxxxxxxxxxxxx
Subject: RE: Threat vector of running a service using a domain account
Saqib,
I believe you're right. Each time I've run cachedump for demonstration
I do not receive hashes for services logging in over the network, I only
receive hashes for interactive users.
Kind Regards,
Scott Ramsdell
-----Original Message-----
From: listbounce@xxxxxxxxxxxxxxxxx [mailto:listbounce@xxxxxxxxxxxxxxxxx]
On Behalf Of Ali, Saqib
Sent: Thursday, September 13, 2007 12:42 PM
To: Jay
Cc: smanaois3@xxxxxxxxx; security-basics@xxxxxxxxxxxxxxxxx
Subject: Re: Threat vector of running a service using a domain account
If a server does cache these creditonals then these can be attackedindependant of the AD and its underlying security controls.
If a service uses domain credential, do those credentials get cached?
I thought only interactive logon credentials are cached.
saqib
http://security-basics.blogspot.com/
- Follow-Ups:
- RE: Threat vector of running a service using a domain account
- From: Roger A. Grimes
- RE: Threat vector of running a service using a domain account
- References:
- Re: Threat vector of running a service using a domain account
- From: Jay
- Re: Threat vector of running a service using a domain account
- From: Ali, Saqib
- RE: Threat vector of running a service using a domain account
- From: Ramsdell, Scott
- RE: Threat vector of running a service using a domain account
- From: Roger A. Grimes
- Re: Threat vector of running a service using a domain account
- Prev by Date: Re: Is Basecamp - risky?
- Next by Date: Re: Remote Access VPN: SDI vs RADIUS for RSA Two Factor Authentication
- Previous by thread: RE: Threat vector of running a service using a domain account
- Next by thread: RE: Threat vector of running a service using a domain account
- Index(es):
Relevant Pages
|