Fun with cached credentials!

From: Firstname Lastname (Todd_Thomas_at_DOH.STATE.FL.US)
Date: 12/03/04

  • Next message: A. Wood: "Workaround for Symantec/Windows Installer Program problems on XP SP2"
    Date:         Fri, 3 Dec 2004 15:01:57 -0500
    To: NTBUGTRAQ@LISTSERV.NTBUGTRAQ.COM
    
    

    One of the security settings on a Windows 2003 box is - Interactive
    logon: Number of previous logons to cache

    I was testing this feature and discovered something that might be
    disturbing to some who are not already aware of it. By default, this
    setting is set to 10, so Windows 2003 will remember 10 sets of logon
    credentials. Some people confuse these credentials with the user
    profiles, but the two do not appear to be synonymous. Some
    experimentation has revealed what I think is a big problem with this
    "feature". Namely, that in an Active Directory setting, users that are
    deleted, or locked in AD can still logon using these cached credentials
    if the system cannot communicate with the Domain Controllers.

    Worse, they continue to be able to logon even if you delete or remove
    their profiles. The credentials are stored somewhere else (probably the
    registry). Thus, unless you take some other remediation deleted Active
    Directory accounts can still logon to systems that are disconnected from
    the Domain FOREVER. Even if you have a password policy that expires
    passwords, that only appears to be enforced if the Domain Controller can
    be contacted. I had no trouble disconnecting the machine and logging in
    with a username long deleted and a password long expired.

    One fix that I found was to change the default setting of the above
    security setting to zero. That seems to cause all previously cached
    credentials to be purged from the system. It also prevents ANYONE from
    logging into the system with a Domain account if the system is not
    actually attached to the domain. This could be a VERY big problem for
    laptop users who do not use local accounts. However, I think this
    setting should be set to zero on any and all servers in an Active
    Directory environment.

    Comments, opinions and further testing results are welcome.

    Todd Thomas
    Disaster Preparedness Consultant

    --
    Editor's Note: The 43rd Most Powerful Person in Networking says...
    Register today to take the TruSecure ICSA exam by 12/31/04  at
    <http://www.2test.com> ,  use promo code "CT1204" and you will pay just
    $221.25 US Dollars for domestic exam delivery and  $296.25 US Dollars
    for international delivery.
    Visit <https://ticsa.trusecure.com>  for complete details regarding the
    TICSA credential and to take the free sample exam.
    --
    

  • Next message: A. Wood: "Workaround for Symantec/Windows Installer Program problems on XP SP2"

    Relevant Pages

    • Re: Problem with control hosted in IE
      ... The control is running on the client machine, so the default credentials are ... These will be the Windows logon from the ... > I logon to another machine using a local account (not one that the IIS ...
      (microsoft.public.dotnet.security)
    • Re: 2003 Web Edition logon errors
      ... > succesfully logon to the machines. ... > users to logon with credentials from domain A. When selecting Domain C ... Unable to obtain Terminal Server User Configuration. ... > the windows 2000 boxes allow users to logon using credentials from ...
      (microsoft.public.win2000.advanced_server)
    • Re: User credential management - system level vs. application level
      ... windows XP embedded, we then launch our application with an entry in the Run ... Switching Windows OS users is slow and causes our application to close ... We end up with two sets of username/password credentials, ... Ideally, we would like to manage logon credentials in one location, allow ...
      (microsoft.public.windowsxp.embedded)
    • =?Utf-8?Q?User_credential_management_=E2=80=93_sys?= =?Utf-8?Q?tem_level_vs._application_lev
      ... windows XP embedded, we then launch our application with an entry in the Run ... Switching Windows OS users is slow and causes our application to close ... We end up with two sets of username/password credentials, ... Ideally, we would like to manage logon credentials in one location, allow ...
      (microsoft.public.windowsxp.embedded)
    • Re: Remote User Needs to Change PWD without connecting to domain
      ... credentials to log on and eventually the password expired. ... > I think you are misinterpreting the "10 logon" settings. ... > Settings, Security Settings, Local Policy, Security Options). ... >> account (note: this should only be temporary as this presents a security ...
      (microsoft.public.win2000.security)