Broken Access Control
Access control enforces policy such that users cannot act outside of their intended permissions. Failures typically lead to unauthorized information disclosure, modification, or destruction of data.
Resumen
Moving up from #5, 94% of applications were tested for some form of broken access control. The 34 CWEs mapped to Broken Access Control had more occurrences in applications than any other category.
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.
Parameter tampering
An attacker modifies URL parameters or hidden form fields to access unauthorized resources. For example, changing an account number in a URL to view another user's data.
Forced browsing
An attacker accesses pages that should require authentication by directly entering the URL, bypassing the intended navigation flow.
Privilege escalation
A standard user gains access to admin functionality by manipulating their role or permissions data.
Cómo Prevenir
- Except for public resources, deny by default
- Implement access control mechanisms once and reuse throughout the application
- Model access controls should enforce record ownership
- Disable web server directory listing and ensure metadata files are not present
- Log access control failures and alert admins when appropriate
- Rate limit API and controller access to minimize automated attack tooling
- Invalidate stateful session identifiers on logout
CWEs con Detección Shoulder (12)
Estos CWEs tienen reglas de detección Shoulder. Haz clic para ver vulnerabilidades específicas y correcciones.
Otros CWEs Mapeados (22)
Estos CWEs están mapeados a esta categoría pero aún no tienen reglas Shoulder.