Skip to main content

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

user
string
Target specific username for AS-REP roasting
users
string
File containing list of usernames to target
ou
string
Target all users in specific organizational unit
domain
string
Target domain (default: current domain)
dc
string
Domain controller to target

Output Options

format
string
Hash output format: john, hashcat (default: hashcat)
outfile
string
Save extracted hashes to file
nowrap
boolean
Don’t wrap long lines in output

Examples

Attack Methodology

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
Vulnerability Condition:
  • “Do not require Kerberos preauthentication” flag set
  • Often configured for compatibility reasons
  • Legacy application requirements
  • Misconfiguration or poor security practices
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
Crackable Format:
  • 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

Account Discovery:
Organizational Unit Targeting:
  • Service account OUs often misconfigured
  • Legacy application account containers
  • Test account organizational units
  • Bulk processing of suspected accounts
Complete Workflow:

Hash Formats

Format Structure:
Cracking Command:
Format Structure:
Cracking Command:

Operational Considerations

Password Complexity:
  • Service accounts often have predictable passwords
  • Legacy accounts may use weak passwords
  • Default passwords in some environments
  • Company-specific password patterns
Account Types:
  • Service accounts (higher success rate)
  • Legacy user accounts
  • Test and development accounts
  • Accounts with compliance exemptions
Authentication Logs:
  • AS-REQ requests appear in domain controller logs
  • Failed pre-authentication events (4771)
  • Unusual authentication patterns
  • High-volume requests from single source
Evasion Strategies:
  • Distribute requests across time
  • Use multiple source systems
  • Target during business hours
  • Limit request frequency

Integration Workflows

Complete Attack Chain:
High-Value Focus:

Defensive Considerations

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
Detection Mechanisms:
  • Monitor for 4771 events (failed pre-authentication)
  • Alert on high-volume AS-REQ requests
  • Track authentication patterns and anomalies
  • Implement behavioral analysis
Immediate Actions:
  • Enable pre-authentication for affected accounts
  • Force password changes for vulnerable accounts
  • Review and update account configurations
  • Implement additional authentication controls
Long-term Improvements:
  • Regular security assessments
  • Automated configuration monitoring
  • Enhanced password policies
  • User and service account management procedures

Troubleshooting

No Vulnerable Accounts:
  • All accounts require pre-authentication
  • Incorrect targeting or enumeration
  • Insufficient domain access
  • Network connectivity issues
Extraction Failures:
  • Account lockout policies triggered
  • Rate limiting by domain controllers
  • Authentication failures
  • Network or DNS issues
Performance Improvements:
  • Use specific domain controllers
  • Optimize request timing
  • Batch process multiple accounts
  • Parallel processing strategies
Success Rate Enhancement:
  • Focus on service accounts
  • Target legacy environments
  • Use company-specific wordlists
  • Implement hybrid attack strategies