Security Misconfiguration
The application might be vulnerable if it is missing appropriate security hardening or has improperly configured permissions on cloud services.
Überblick
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.
Wie Angreifer dies ausnutzen
Das Verstehen von Angriffsmustern hilft Ihnen, bessere Verteidigungen aufzubauen. Dies sind die Techniken, die Sicherheitsteams überwachen.
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.
Wie Sie vorbeugen
- 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 mit Shoulder-Erkennung (6)
Diese CWEs haben Shoulder-Erkennungsregeln. Klicken Sie, um spezifische Schwachstellen und Korrekturen zu sehen.
Andere zugeordnete CWEs (14)
Diese CWEs sind dieser Kategorie zugeordnet, haben aber noch keine Shoulder-Regeln.