Security Misconfiguration
The application might be vulnerable if it is missing appropriate security hardening or has improperly configured permissions on cloud services.
Overview
Moving up from #6, 90% of applications were tested for some form of misconfiguration. With more shifts into highly configurable software, it's not surprising to see this category move up.
How Attackers Exploit This
Understanding attack patterns helps you build better defenses. These are the techniques security teams watch for.
Default credentials
Administrative interfaces or services are left with default usernames and passwords that are publicly known.
Verbose error messages
Detailed error messages expose internal paths, stack traces, or database schemas to attackers.
Unnecessary services
Debug endpoints, sample applications, or development features are left enabled in production.
How to Prevent
- Implement a repeatable hardening process for fast, secure deployment
- Remove or do not install unused features and frameworks
- Review and update configurations appropriate to all security notes
- Use segmented application architecture for effective separation
- Send security directives to clients (Security Headers)
- Automate verification of configurations in all environments
CWEs with Shoulder Detection (6)
These CWEs have Shoulder detection rules. Click to see specific vulnerabilities and fixes.
Other Mapped CWEs (14)
These CWEs are mapped to this category. Use MITRE references for guidance.