Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cyberstrikeus/T1003.005_cached-domain-credentials
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
Passed 19 of 22 test cases with the skill, and 18 of 22 without it.
and 2 more in the full report
3 fixed16 passed either way1 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
We run Quest Authentication Services (formerly VAS) across our Unix/Linux server farm to join them to Active Directory. Admins assume Quest stores credentials in `/etc/opt/quest/vas.conf` accessible by any local user. Where on the local filesystem does Quest store its authentication cache database containing domain hashes, and what privilege level is needed to access it? Format the response as a short technical advisory.
| Checked | Without skill | With skill |
|---|---|---|
| Specifies the Quest VAS cache path as /var/opt/quest/vas/authcache/vas_auth.vdb. | Missed | Passed |
| Indicates that root or sudo access is required to extract the cached credentials. | Passed | Passed |
The instructions your model reads when the skill loads.
Sub-technique of: T1003
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
On Windows Vista and newer, the hash format is DCC2 (Domain Cached Credentials version 2) hash, also known as MS-Cache v2 hash. The number of default cached credentials varies and can be altered per system. This hash does not allow pass-the-hash style attacks, and instead requires Password Cracking to recover the plaintext password.
On Linux systems, Active Directory credentials can be accessed through caches maintained by software like System Security Services Daemon (SSSD) or Quest Authentication Services (formerly VAS). Cached credential hashes are typically located at /var/lib/sss/db/cache.[domain].ldb for SSSD or /var/opt/quest/vas/authcache/vas_auth.vdb for Quest. Adversaries can use utilities, such as tdbdump, on these database files to dump the cached hashes and use Password Cracking to obtain the plaintext password.
With SYSTEM or sudo access, the tools/utilities such as Mimikatz, Reg, and secretsdump.py for Windows or Linikatz for Linux can be used to extract the cached credentials.
Note: Cached credentials for Windows Vista are derived using PBKDF2.
Platforms: Windows, Linux
The following tests are from Atomic Red Team and provide actionable ways to test this technique:
List credentials currently stored on the host via the built-in Windows utility cmdkey.exe Credentials listed with Cmdkey only pertain to the current user
test cases passed, vs 18 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.