Skip to main content

Overview

List Kerberos tickets in the current logon session or a specified LUID. This command provides detailed information about cached tickets including service names, encryption types, and validity periods.

Syntax

Optional Parameters

luid
string
Target specific logon session ID (requires elevation)
user
string
Filter tickets by specific username
service
string
Filter tickets by service name pattern

Examples

Ticket Information

Basic Information:
  • Client name and realm
  • Server name and realm
  • Encryption type (RC4, AES128, AES256)
  • Key version number (kvno)
Timing Information:
  • Start time (valid from)
  • End time (expires)
  • Renew time (renewable until)
  • Current validity status
Technical Details:
  • Ticket cache location
  • Ticket flags and attributes
  • Session key information
  • Authorization data presence

Use Cases

Authentication Status:
  • Verify successful authentication
  • Check current access permissions
  • Validate ticket injection success
  • Monitor session state changes
Troubleshooting:
  • Debug authentication failures
  • Identify expired tickets
  • Verify service access capabilities
  • Check encryption compatibility
Security Assessment:
  • Inventory available access
  • Identify privilege boundaries
  • Map service relationships
  • Track authentication history
Planning and Cleanup:
  • Plan ticket extraction targets
  • Verify cleanup effectiveness
  • Monitor persistent access
  • Assess operational security

Session Targeting

Standard Operation:
  • Lists tickets from current user session
  • No special privileges required
  • Safe reconnaissance operation
  • Limited to user context
Information Available:
  • TGT for current domain
  • Service tickets for accessed resources
  • Cross-realm tickets if applicable
  • Delegation tickets if authorized
Elevated Requirements:
  • Requires administrative privileges
  • Can target any logon session
  • System-wide ticket visibility
  • Enhanced reconnaissance capabilities
LUID Discovery:

Output Analysis

Sample Output:
Key Elements:
  • Ticket number for extraction reference
  • Service access scope
  • Encryption strength assessment
  • Validity window analysis
  • Flag configuration review

Integration Workflows

Target Identification:
Success Validation:

Ticket Types

Identification:
  • Server: krbtgt/DOMAIN.LOCAL
  • Provides broad authentication capabilities
  • Renewable for extended validity
  • Foundation for service ticket requests
Strategic Value:
  • Enables lateral movement
  • Supports privilege escalation
  • Allows service enumeration
  • Facilitates persistence
Common Services:
  • CIFS (file sharing)
  • HOST (administrative access)
  • LDAP (directory services)
  • HTTP (web applications)
  • MSSQL (database access)
Access Implications:
  • Direct service authentication
  • Specific resource access
  • Limited scope operations
  • Immediate usability

Operational Security

Low-Risk Operations:
  • Standard Windows API usage
  • Normal authentication queries
  • Minimal log generation
  • Difficult to distinguish from legitimate activity
Best Practices:
  • Use during business hours
  • Limit frequency of queries
  • Avoid automated scripting patterns
  • Correlate with normal user behavior
  • dump - Extract listed tickets
  • triage - Cross-session ticket overview
  • ptt - Inject tickets into session
  • purge - Clear ticket cache