Related skills: Middleware vulnerabilities (exploitation after default credentials) →
middleware-exploit; Database attacks (direct connection with default credentials) →database-exploit; Credential spraying →cred-spray
Default credentials are the lowest-cost attack vector—they do not trigger WAFs, do not require vulnerabilities, and have a success rate far beyond expectations. Many administrators never change passwords after deployment.
Phase 1: Service Identification and Prioritization
First identify all services on the target that require authentication, and rank them by value:
| Priority | Service Type | Reason |
|---|---|---|
| P0 | Web admin panel | Usually has the highest privileges and can read and write all data |
| P0 | Database (MySQL/PostgreSQL/MSSQL) | Directly read the flag or user data |
| P1 | Middleware (Tomcat/Jenkins/WebLogic) | Can deploy a webshell or execute commands |
| P1 | SSH/FTP/RDP | Directly obtain a system shell |
| P2 | Redis/Memcached/MongoDB | May have no authentication, or use default passwords |
| P2 | IoT/router/printer Web UI | Passwords are often never changed |
Phase 2: Default Credential Dictionaries
Web admin panel
admin:admin admin:password admin:123456
admin:admin123 admin:Admin@123 admin:P@ssw0rd
root:root root:toor root:password
administrator:admin test:test user:user
guest:guest demo:demo
Also try empty passwords — some CMSs (such as WordPress on first installation) may have no password.
Database
| Service | Default credentials | Notes |
|---|---|---|
| MySQL | root:root, root: (empty), root:mysql, root:123456 |
5.7+ sets a password during installation; older versions are often empty |
| PostgreSQL | postgres:postgres, postgres: (empty) |
Local trust authentication may require no password |
| MSSQL | sa:sa, sa:Password123, sa:1 |
sa is the highest privilege |
| Redis | No authentication (no password required by default) | Connect directly to test |
| MongoDB | No authentication (no password required by default) | mongosh --host target |
| Elasticsearch | No authentication (default for <8.0) | curl target:9200 |
Middleware
| Service | Default credentials | Key path |
|---|---|---|
| Tomcat | tomcat:tomcat, admin:admin, manager:manager |
/manager/html |
| Jenkins | No authentication or admin:admin |
/script (Groovy console) |
| WebLogic | weblogic:weblogic1, weblogic:welcome1 |
/console |
| JBoss | No authentication | /jmx-console |
| Grafana | admin:admin |
/login |
| Zabbix | Admin:zabbix |
/zabbix |
Remote services
| Service | Default credentials |
|---|---|
| SSH | root:root, root:toor, admin:admin, ubuntu:ubuntu |
| FTP | anonymous: (anonymous login), ftp:ftp, admin:admin |
| VNC | Empty password, password, 1234 |
| SMB | guest: (empty), administrator:password |
Phase 3: Testing Strategy
3.1 Manual testing first
First manually test the 3-5 most common default credentials—do not start by running brute-force tools. Reasons:
- Default credentials have a high hit rate, and 3 attempts are enough
- Does not trigger lockout policies
- Faster than configuring a brute-force tool
3.2 Lockout evasion
Before brute-forcing, you must confirm the lockout policy:
- Observe the response: whether "account locked" or a CAPTCHA appears after 3-5 consecutive failures
- If there is a lockout: try only the 2-3 most likely passwords per account, then switch to the next account
- Password spraying(Password Spraying): Fix one password (e.g.,
admin), iterate through all usernames—safer than fixing a username and iterating passwords - Custom wordlist: If you have target personal information (name/birthday/phone), use
ccupp generateto generate a social engineering wordlist, which is much more precise than a generic wordlist
3.3 Credential Reuse
After discovering a set of valid credentials,test the same username and password on all other services. Administrators often use the same password across multiple services.
Phase 4: Post-Exploitation
After discovering valid credentials:
- Use
evidence_saveto save credentials - Confirm the privilege level (regular user/administrator)
- If a regular user → refer to
privilege-escalation-webfor privilege escalation - If an administrator → look for flags, sensitive data, and further penetration entry points
- If a database → directly query the flag table or user table
Precautions
- Default credential testing should be performed at thevery beginningof a penetration test, after port scanning and before exploitation
- Do not skip services that "don't seem important"—monitoring systems such as Grafana/Zabbix often contain internal network information
- In cloud environments, watch out for metadata credential leakage (refer to
cloud-metadata)