Security Misconfiguration
The application might be vulnerable if it is missing appropriate security hardening or has improperly configured permissions on cloud services.
Visão Geral
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.
Como Atacantes Exploram Isso
Entender padrões de ataque ajuda você a construir melhores defesas. Estas são as técnicas que equipes de segurança monitoram.
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.
Como 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 com Detecção Shoulder (6)
Estes CWEs têm regras de detecção Shoulder. Clique para ver vulnerabilidades específicas e correções.
Outros CWEs Mapeados (14)
Estes CWEs estão mapeados para esta categoria mas ainda não têm regras Shoulder.