Ejecuta análisis estático (SAST) sobre el código buscando el patrón inseguro en el flujo de datos.
CWE-279 Variante Borrador
Incorrect Execution-Assigned Permissions
This vulnerability occurs when a running application incorrectly changes an object's access permissions, overriding the security settings that a user or administrator intentionally configured.
Definición
What is CWE-279?
This vulnerability occurs when a running application incorrectly changes an object's access permissions, overriding the security settings that a user or administrator intentionally configured.
This flaw typically happens during an application's runtime operations, such as when it creates temporary files, spawns new processes, or modifies system resources. Instead of respecting the principle of least privilege, the software assigns broader permissions—like making a file world-writable or granting excessive privileges to a process—than what was originally intended. This creates a window of opportunity where unauthorized users or processes can read, modify, or execute sensitive resources.
To prevent this, developers must ensure that permission assignments are explicit, validated, and adhere strictly to the user-specified security policy throughout the entire lifecycle of an object. Code should avoid implicit or default permission settings during execution, and security-critical functions must consistently check and apply the correct, minimal permissions required for the task.
Impacto en el mundo real
Real-world CVEs caused by CWE-279
-
Log files opened read/write.
-
Log files opened read/write.
-
Log files opened read/write.
Cómo lo explotan los atacantes
Ruta del atacante paso a paso
- 1
Identifica una ruta de código que maneje entrada no confiable sin validación.
- 2
Crea un payload que ejercite el comportamiento inseguro — inyección, traversal, overflow o abuso de lógica.
- 3
Envía el payload a través de una solicitud normal y observa la reacción de la aplicación.
- 4
Itera hasta que la respuesta filtre datos, ejecute código del atacante o escale privilegios.
Ejemplo de código vulnerable
Vulnerable pseudo
MITRE no ha publicado un ejemplo de código para esta CWE. El patrón siguiente es ilustrativo — consulta Recursos para referencias canónicas.
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
// Untrusted input flows directly into the sensitive sink.
return executeUnsafe(input);
} Ejemplo de código seguro
Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Lista de prevención
How to prevent CWE-279
- Architecture and Design / Operation Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Architecture and Design Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
Señales de detección
How to detect CWE-279
Ejecuta pruebas dinámicas de seguridad de aplicaciones (DAST) contra el endpoint en vivo.
Vigila los logs en tiempo de ejecución para detectar trazas de excepción inusuales, entradas malformadas o intentos de bypass de autorización.
Revisión de código: marca cualquier código nuevo que maneje entrada desde esta superficie sin usar los helpers validados del framework.
CWE-279
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Preguntas frecuentes ¿Qué es CWE-279?
¿Qué gravedad tiene CWE-279?
¿Qué lenguajes o plataformas se ven afectados por CWE-279?
¿Cómo puedo prevenir CWE-279?
¿Cómo detecta y corrige Plexicus CWE-279?
¿Dónde puedo aprender más sobre CWE-279?
Frequently asked questions
¿Qué es CWE-279?
This vulnerability occurs when a running application incorrectly changes an object's access permissions, overriding the security settings that a user or administrator intentionally configured.
¿Qué gravedad tiene CWE-279?
MITRE no ha publicado una calificación de probabilidad de explotación para esta debilidad. Trátala como de impacto medio hasta que tu modelo de amenazas demuestre lo contrario.
¿Qué lenguajes o plataformas se ven afectados por CWE-279?
MITRE no ha especificado plataformas afectadas para esta CWE — puede aplicar a la mayoría de los stacks de aplicaciones.
¿Cómo puedo prevenir CWE-279?
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software. Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and…
¿Cómo detecta y corrige Plexicus CWE-279?
El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-279 en cada commit. Cuando hay coincidencia, nuestro agente Codex Remedium abre un PR de corrección con el código corregido, las pruebas y un resumen de una línea para el revisor.
¿Dónde puedo aprender más sobre CWE-279?
MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/279.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.
Debilidades relacionadas
Weaknesses related to CWE-279
CWE-732 Padre
Incorrect Permission Assignment for Critical Resource
This vulnerability occurs when a system grants overly permissive access to a sensitive resource, allowing unauthorized users or processes…
CWE-1004 Hermano
Sensitive Cookie Without 'HttpOnly' Flag
This vulnerability occurs when an application stores sensitive data in a cookie but fails to set the 'HttpOnly' flag, leaving the cookie…
CWE-276 Hermano
Incorrect Default Permissions
This vulnerability occurs when software installation scripts set overly permissive file or directory access rights by default. Instead of…
CWE-277 Hermano
Insecure Inherited Permissions
This vulnerability occurs when an application sets default file or directory permissions that are too permissive, and these insecure…
CWE-278 Hermano
Insecure Preserved Inherited Permissions
This vulnerability occurs when a software product copies or extracts files while unintentionally preserving insecure permissions from…
CWE-281 Hermano
Improper Preservation of Permissions
This vulnerability occurs when a system fails to correctly maintain file or object permissions during operations like copying, sharing, or…
CWE-766 Hermano
Critical Data Element Declared Public
This vulnerability occurs when a critical piece of data—like a variable, field, or class member—is mistakenly declared as public when it…
¿Listo para validar lo que importa?
Listo para validar lo que importa.
Plexicus es Proof-Driven AppSec: hallazgos validados, comprensión contextual y remediación revisada — anclada en evidencia, acotada contigo.