Security Misconfiguration
The application might be vulnerable if it is missing appropriate security hardening or has improperly configured permissions on cloud services.
Aperçu
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.
Comment les Attaquants Exploitent Cela
Comprendre les patterns d'attaque vous aide à construire de meilleures défenses. Ce sont les techniques que les équipes de sécurité surveillent.
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.
Comment Prévenir
- 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 avec Détection Shoulder (6)
Ces CWEs ont des règles de détection Shoulder. Cliquez pour voir les vulnérabilités spécifiques et les correctifs.
Autres CWEs Associés (14)
Ces CWEs sont associés à cette catégorie mais n'ont pas encore de règles Shoulder.