Executar análise estática (SAST) na base de código à procura do padrão inseguro no fluxo de dados.
CWE-1078 Classe 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.
Definição
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 no mundo real
Real-world CVEs caused by CWE-1078
Ainda não há referências CVE públicas associadas a este CWE no catálogo da MITRE.
Como os atacantes a exploram
Trajeto do atacante passo a passo
- 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.
Exemplo de código vulnerável
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); Exemplo 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 verificação de prevenção
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.
Sinais de deteção
How to detect CWE-1078
Executar testes dinâmicos de segurança de aplicações (DAST) contra o endpoint em execução.
Monitorizar os registos em tempo de execução para traços de exceção invulgares, input malformado ou tentativas de contornar a autorização.
Revisão de código: sinalizar qualquer novo código que trate input desta superfície sem usar os ajudantes validados do 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.
Perguntas frequentes O que é o CWE-1078?
Qual a gravidade do CWE-1078?
Que linguagens ou plataformas são afetadas pelo CWE-1078?
Como posso prevenir o CWE-1078?
Como é que o Plexicus deteta e corrige o CWE-1078?
Onde posso saber mais sobre o CWE-1078?
Frequently asked questions
O que é o 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.
Qual a gravidade do CWE-1078?
A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.
Que linguagens ou plataformas são afetadas pelo CWE-1078?
A MITRE não especificou as plataformas afetadas por este CWE — pode aplicar-se à maioria das stacks de aplicações.
Como posso prevenir o 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.
Como é que o Plexicus deteta e corrige o CWE-1078?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-1078 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.
Onde posso saber mais sobre o CWE-1078?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/1078.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-1078
CWE-1076 Pai
Insufficient Adherence to Expected Conventions
This weakness occurs when software code, design, documentation, or other components fail to follow established industry or…
CWE-1045 Irmão
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 Irmão
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 Irmão
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 Irmão
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 Irmão
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 Irmão
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 Irmão
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 Irmão
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.
Pronto para validar o que importa?
Pronto para validar o que importa.
O Plexicus é Proof-Driven AppSec: achados validados, compreensão contextual e remediação revisada — ancorada em evidência, escopada com você.