Overview
AS-REP roasting attacks target user accounts that do not require Kerberos pre-authentication. This vulnerability allows attackers to request AS-REP responses containing encrypted data that can be cracked offline to recover plaintext passwords.Syntax
Targeting Options
Target specific username for AS-REP roasting
File containing list of usernames to target
Target all users in specific organizational unit
Target domain (default: current domain)
Domain controller to target
Output Options
Hash output format: john, hashcat (default: hashcat)
Save extracted hashes to file
Don’t wrap long lines in output
Examples
Attack Methodology
Pre-Authentication Vulnerability
Pre-Authentication Vulnerability
Security Mechanism:
- Kerberos pre-authentication requires proof of password knowledge
- Prevents offline attacks by default
- Enabled for all accounts by standard policy
- Critical security control for authentication
- “Do not require Kerberos preauthentication” flag set
- Often configured for compatibility reasons
- Legacy application requirements
- Misconfiguration or poor security practices
AS-REP Structure
AS-REP Structure
Encrypted Component:
- AS-REP contains user session key encrypted with user’s password hash
- Encryption uses user’s long-term key (NT hash)
- No salt or strong encryption by default
- Vulnerable to offline cracking attacks
- Hashcat mode 18200 (Kerberos 5, etype 23, AS-REP)
- John the Ripper krb5asrep format
- Standard dictionary and rule-based attacks
- GPU acceleration support
Target Discovery
LDAP Enumeration
LDAP Enumeration
Account Discovery:Organizational Unit Targeting:
- Service account OUs often misconfigured
- Legacy application account containers
- Test account organizational units
- Bulk processing of suspected accounts
Integration with Discovery
Integration with Discovery
Complete Workflow:
Hash Formats
Hashcat Format (Default)
Hashcat Format (Default)
Format Structure:Cracking Command:
John the Ripper Format
John the Ripper Format
Format Structure:Cracking Command:
Operational Considerations
Success Rate Factors
Success Rate Factors
Password Complexity:
- Service accounts often have predictable passwords
- Legacy accounts may use weak passwords
- Default passwords in some environments
- Company-specific password patterns
- Service accounts (higher success rate)
- Legacy user accounts
- Test and development accounts
- Accounts with compliance exemptions
Detection and Noise
Detection and Noise
Authentication Logs:
- AS-REQ requests appear in domain controller logs
- Failed pre-authentication events (4771)
- Unusual authentication patterns
- High-volume requests from single source
- Distribute requests across time
- Use multiple source systems
- Target during business hours
- Limit request frequency
Integration Workflows
Discovery to Exploitation
Discovery to Exploitation
Complete Attack Chain:
Targeted Approach
Targeted Approach
High-Value Focus:
Defensive Considerations
Attack Prevention
Attack Prevention
Configuration Hardening:
- Ensure pre-authentication required for all accounts
- Regular audit of userAccountControl attributes
- Monitor for accounts with UF_DONT_REQUIRE_PREAUTH flag
- Implement strong password policies
- Monitor for 4771 events (failed pre-authentication)
- Alert on high-volume AS-REQ requests
- Track authentication patterns and anomalies
- Implement behavioral analysis
Remediation
Remediation
Immediate Actions:
- Enable pre-authentication for affected accounts
- Force password changes for vulnerable accounts
- Review and update account configurations
- Implement additional authentication controls
- Regular security assessments
- Automated configuration monitoring
- Enhanced password policies
- User and service account management procedures
Troubleshooting
Common Issues
Common Issues
No Vulnerable Accounts:
- All accounts require pre-authentication
- Incorrect targeting or enumeration
- Insufficient domain access
- Network connectivity issues
- Account lockout policies triggered
- Rate limiting by domain controllers
- Authentication failures
- Network or DNS issues
Optimization
Optimization
Performance Improvements:
- Use specific domain controllers
- Optimize request timing
- Batch process multiple accounts
- Parallel processing strategies
- Focus on service accounts
- Target legacy environments
- Use company-specific wordlists
- Implement hybrid attack strategies
Related Commands
preauthscan- Discover vulnerable accountsasktgt- Use cracked credentialskerberoast- Alternative roasting techniquebrute- Password bruteforce attacks