Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.
CWE-188 Base Rascunho
Reliance on Data/Memory Layout
This vulnerability occurs when software incorrectly assumes how data is structured in memory or within network packets, leading to unexpected behavior when those underlying layouts change.
Definição
What is CWE-188?
This vulnerability occurs when software incorrectly assumes how data is structured in memory or within network packets, leading to unexpected behavior when those underlying layouts change.
At the system level, memory layout is not universal. Different compilers, architectures, or platform updates can change how variables are ordered, aligned, or padded in memory. For example, one system might place two variables adjacent to each other, while another inserts space between them for performance alignment. If your code assumes a specific, fixed arrangement—like calculating offsets between variables—it will break when ported or run in a different environment, potentially reading corrupt data or causing crashes.
In network protocols, similar risks exist when parsing messages. Developers often use fixed offsets relative to known header fields to locate specific data. However, new protocol versions, optional extensions, or edge cases can introduce unexpected padding or reorder fields. This causes the software to misinterpret packet contents, treating one type of data (like a length field) as another (like payload data), which can lead to security flaws like information disclosure or denial of service.
Impacto no mundo real
Real-world CVEs caused by CWE-188
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
Identificar um caminho de código que trata input não confiável sem validação.
- 2
Criar um payload que explora o comportamento inseguro — injeção, traversal, overflow ou abuso de lógica.
- 3
Entregar o payload através de um pedido normal e observar a reação da aplicação.
- 4
Iterar até que a resposta exponha dados, execute código do atacante ou escale privilégios.
Exemplo de código vulnerável
Vulnerable C
In this example function, the memory address of variable b is derived by adding 1 to the address of variable a. This derived address is then used to assign the value 0 to b.
void example() {
char a;
char b;
*(&a + 1) = 0;
} Exemplo 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 verificação de prevenção
How to prevent CWE-188
- Implementation / Architecture and Design In flat address space situations, never allow computing memory addresses as offsets from another memory address.
- Architecture and Design Fully specify protocol layout unambiguously, providing a structured grammar (e.g., a compilable yacc grammar).
- Testing Testing: Test that the implementation properly handles each case in the protocol grammar.
Sinais de deteção
How to detect CWE-188
CWE-188
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-188?
Qual a gravidade do CWE-188?
Que linguagens ou plataformas são afetadas pelo CWE-188?
Como posso prevenir o CWE-188?
Como é que o Plexicus deteta e corrige o CWE-188?
Onde posso saber mais sobre o CWE-188?
Frequently asked questions
O que é o CWE-188?
This vulnerability occurs when software incorrectly assumes how data is structured in memory or within network packets, leading to unexpected behavior when those underlying layouts change.
Qual a gravidade do CWE-188?
A MITRE classifica a probabilidade de exploração como Baixa — a exploração é pouco comum, mas a fraqueza deve mesmo assim ser corrigida quando descoberta.
Que linguagens ou plataformas são afetadas pelo CWE-188?
MITRE lists the following affected platforms: C, C++.
Como posso prevenir o CWE-188?
In flat address space situations, never allow computing memory addresses as offsets from another memory address. Fully specify protocol layout unambiguously, providing a structured grammar (e.g., a compilable yacc grammar).
Como é que o Plexicus deteta e corrige o CWE-188?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-188 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-188?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/188.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-188
CWE-1105 Pai
Insufficient Encapsulation of Machine-Dependent Functionality
This weakness occurs when an application relies on hardware-specific or platform-dependent features but fails to isolate that code from…
CWE-198 Filho
Use of Incorrect Byte Ordering
This vulnerability occurs when software processes data from another system without considering byte order (endianness), such as big-endian…
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ê.