Ejecuta análisis estático (SAST) sobre el código buscando el patrón inseguro en el flujo de datos.
CWE-1078 Clase Incompleto
Inappropriate Source Code Style or Formatting
This weakness occurs when source code violates established style guidelines for formatting, indentation, whitespace, or commenting, making it difficult to read and maintain.
Definición
What is CWE-1078?
This weakness occurs when source code violates established style guidelines for formatting, indentation, whitespace, or commenting, making it difficult to read and maintain.
While inconsistent formatting doesn't directly cause security vulnerabilities, it creates a breeding ground for them. Poorly structured code is harder to review, making subtle logic flaws, missing security checks, or unintended behaviors much easier to miss during manual inspection or automated analysis. This readability deficit directly undermines the team's ability to identify and fix critical security issues before deployment.
Addressing this requires integrating automated style checkers and formatters into the development workflow. Tools like linters and code formatters enforce consistency automatically, ensuring the codebase remains clean and reviewable. This proactive practice reduces cognitive load for developers, accelerates code reviews, and significantly improves the team's overall capacity to spot and remediate genuine security defects hidden within complex logic.
Impacto en el mundo real
Real-world CVEs caused by CWE-1078
Todavía no hay CVEs públicos enlazados a esta CWE en el catálogo de MITRE.
Cómo lo explotan los atacantes
Ruta del atacante paso a paso
- 1
The usage of symbolic names instead of hard-coded constants is preferred.
- 2
The following is an example of using a hard-coded constant instead of a symbolic name.
- 3
If the buffer value needs to be changed, then it has to be altered in more than one place. If the developer forgets or does not find all occurrences, in this example it could lead to a buffer overflow.
- 4
In this example the developer will only need to change one value and all references to the buffer size are updated, as a symbolic name is used instead of a hard-coded constant.
Ejemplo de código vulnerable
Vulnerable C
The following is an example of using a hard-coded constant instead of a symbolic name.
char buffer[1024];
...
fgets(buffer, 1024, stdin); Ejemplo de código seguro
Secure C
If the buffer value needs to be changed, then it has to be altered in more than one place. If the developer forgets or does not find all occurrences, in this example it could lead to a buffer overflow.
enum { MAX_BUFFER_SIZE = 1024 };
...
char buffer[MAX_BUFFER_SIZE];
...
fgets(buffer, MAX_BUFFER_SIZE, stdin); 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-1078
- Architecture Use safe-by-default frameworks and APIs that prevent the unsafe pattern from being expressible.
- Implementation Validate input at trust boundaries; use allowlists, not denylists.
- Implementation Apply the principle of least privilege to credentials, file paths, and runtime permissions.
- Testing Cover this weakness in CI: SAST rules + targeted unit tests for the data flow.
- Operation Monitor logs for the runtime signals listed in the next section.
Señales de detección
How to detect CWE-1078
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-1078
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-1078?
¿Qué gravedad tiene CWE-1078?
¿Qué lenguajes o plataformas se ven afectados por CWE-1078?
¿Cómo puedo prevenir CWE-1078?
¿Cómo detecta y corrige Plexicus CWE-1078?
¿Dónde puedo aprender más sobre CWE-1078?
Frequently asked questions
¿Qué es CWE-1078?
This weakness occurs when source code violates established style guidelines for formatting, indentation, whitespace, or commenting, making it difficult to read and maintain.
¿Qué gravedad tiene CWE-1078?
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-1078?
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-1078?
Use safe-by-default frameworks, validate untrusted input at trust boundaries, and apply the principle of least privilege. Cover the data-flow signature in CI with SAST.
¿Cómo detecta y corrige Plexicus CWE-1078?
El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-1078 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-1078?
MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/1078.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.
Debilidades relacionadas
Weaknesses related to CWE-1078
CWE-1076 Padre
Insufficient Adherence to Expected Conventions
This weakness occurs when software code, design, documentation, or other components fail to follow established industry or…
CWE-1045 Hermano
Parent Class with a Virtual Destructor and a Child Class without a Virtual Destructor
This occurs when a base class defines a virtual destructor, but a derived class inherits from it without declaring its own virtual…
CWE-1070 Hermano
Serializable Data Element Containing non-Serializable Item Elements
This weakness occurs when a class or data structure is marked as serializable, but it contains one or more member elements that cannot be…
CWE-1079 Hermano
Parent Class without Virtual Destructor Method
This occurs when a base class, designed to be inherited from, does not declare its destructor as virtual. This oversight prevents proper…
CWE-1082 Hermano
Class Instance Self Destruction Control Element
This vulnerability occurs when an object's code contains logic that triggers its own deletion or destruction during runtime.
CWE-1087 Hermano
Class with Virtual Method without a Virtual Destructor
This occurs when a class defines a virtual method but does not also provide a virtual destructor.
CWE-1091 Hermano
Use of Object without Invoking Destructor Method
This weakness occurs when a program accesses an object but fails to properly call its destructor or finalizer method. This leaves the…
CWE-1097 Hermano
Persistent Storable Data Element without Associated Comparison Control Element
This weakness occurs when a persistent data object lacks the necessary methods to be properly compared, which can lead to inconsistent or…
CWE-1098 Hermano
Data Element containing Pointer Item without Proper Copy Control Element
This weakness occurs when a data structure contains a pointer, but the code lacks proper methods to copy or initialize that pointer safely.
¿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.