Security Misconfiguration
The application might be vulnerable if it is missing appropriate security hardening or has improperly configured permissions on cloud services.
Resumen
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.
Cómo los Atacantes Explotan Esto
Entender los patrones de ataque te ayuda a construir mejores defensas. Estas son las técnicas que los equipos de seguridad vigilan.
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.
Cómo Prevenir
- 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 con Detección Shoulder (6)
Estos CWEs tienen reglas de detección Shoulder. Haz clic para ver vulnerabilidades específicas y correcciones.
Otros CWEs Mapeados (14)
Estos CWEs están mapeados a esta categoría pero aún no tienen reglas Shoulder.