CWE-14 Variante Borrador

Compiler Removal of Code to Clear Buffers

A compiler optimization can remove security-critical code intended to wipe sensitive data from memory, leaving secrets exposed. This happens when the compiler identifies buffer-clearing operations…

Definición

What is CWE-14?

A compiler optimization can remove security-critical code intended to wipe sensitive data from memory, leaving secrets exposed. This happens when the compiler identifies buffer-clearing operations as unnecessary 'dead stores' and eliminates them.
This vulnerability occurs in a three-step scenario. First, your application stores confidential information like passwords, encryption keys, or tokens in memory. Then, as a security best practice, your source code explicitly overwrites that memory location to scrub the data. However, an optimizing compiler analyzes the code, sees the memory isn't read again after being overwritten, and decides the overwrite operation is a 'dead store'—a redundant write to a variable that is never used. To improve performance, the compiler silently removes this crucial cleanup instruction from the final executable, leaving the secret data intact in memory where it could be dumped or leaked. For developers, this is a critical pitfall because your source code appears secure, but the compiled binary behaves differently. You cannot rely on standard memory-zeroing functions in performance-sensitive or optimized release builds without taking special precautions. Mitigating this requires using compiler-specific directives (like `volatile` pointers), dedicated secure memory-wiping functions designed to survive optimization, or disabling specific optimizations for the sensitive code sections to ensure your cleanup logic is executed as intended.
Impacto en el mundo real

Real-world CVEs caused by CWE-14

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. 1

    The following code reads a password from the user, uses the password to connect to a back-end mainframe and then attempts to scrub the password from memory using memset().

  2. 2

    The code in the example will behave correctly if it is executed verbatim, but if the code is compiled using an optimizing compiler, such as Microsoft Visual C++ .NET or GCC 3.x, then the call to memset() will be removed as a dead store because the buffer pwd is not used after its value is overwritten [18]. Because the buffer pwd contains a sensitive value, the application may be vulnerable to attack if the data are left memory resident. If attackers are able to access the correct region of memory, they may use the recovered password to gain control of the system.

  3. 3

    It is common practice to overwrite sensitive data manipulated in memory, such as passwords or cryptographic keys, in order to prevent attackers from learning system secrets. However, with the advent of optimizing compilers, programs do not always behave as their source code alone would suggest. In the example, the compiler interprets the call to memset() as dead code because the memory being written to is not subsequently used, despite the fact that there is clearly a security motivation for the operation to occur. The problem here is that many compilers, and in fact many programming languages, do not take this and other security concerns into consideration in their efforts to improve efficiency.

  4. 4

    Attackers typically exploit this type of vulnerability by using a core dump or runtime mechanism to access the memory used by a particular application and recover the secret information. Once an attacker has access to the secret information, it is relatively straightforward to further exploit the system and possibly compromise other resources with which the application interacts.

Ejemplo de código vulnerable

Vulnerable C

The following code reads a password from the user, uses the password to connect to a back-end mainframe and then attempts to scrub the password from memory using memset().

Vulnerable C 
void GetData(char *MFAddr) {
  		char pwd[64];
  		if (GetPasswordFromUser(pwd, sizeof(pwd))) {
  				if (ConnectToMainframe(MFAddr, pwd)) {
```
// Interaction with mainframe* 
  						}}
  		memset(pwd, 0, sizeof(pwd));}
Ejemplo de código seguro

Secure pseudo

Seguro 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-14

  • Implementation Store the sensitive data in a "volatile" memory location if available.
  • Build and Compilation If possible, configure your compiler so that it does not remove dead stores.
  • Architecture and Design Where possible, encrypt sensitive data that are used by a software system.
Señales de detección

How to detect CWE-14

Black Box

This specific weakness is impossible to detect using black box methods. While an analyst could examine memory to see that it has not been scrubbed, an analysis of the executable would not be successful. This is because the compiler has already removed the relevant code. Only the source code shows whether the programmer intended to clear the memory or not, so this weakness is indistinguishable from others.

White Box

This weakness is only detectable using white box methods (see black box detection factor). Careful analysis is required to determine if the code is likely to be removed by the compiler.

Auto-corrección de Plexicus

Plexicus detecta automáticamente CWE-14 y abre un PR de corrección en menos de 60 segundos.

Codex Remedium escanea cada commit, identifica esta debilidad concreta y entrega un pull request listo para revisión con el parche. Sin tickets. Sin traspasos.

Solicitar demo Probar Plexicus gratis
Preguntas frecuentes

Frequently asked questions

¿Qué es CWE-14?

A compiler optimization can remove security-critical code intended to wipe sensitive data from memory, leaving secrets exposed. This happens when the compiler identifies buffer-clearing operations as unnecessary 'dead stores' and eliminates them.

¿Qué gravedad tiene CWE-14?

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-14?

MITRE lists the following affected platforms: C, C++.

¿Cómo puedo prevenir CWE-14?

Store the sensitive data in a "volatile" memory location if available. If possible, configure your compiler so that it does not remove dead stores.

¿Cómo detecta y corrige Plexicus CWE-14?

El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-14 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-14?

MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/14.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.

Debilidades relacionadas

Weaknesses related to CWE-14

CWE-733 Padre

Compiler Optimization Removal or Modification of Security-critical Code

This vulnerability occurs when a compiler's optimization process unintentionally strips out or alters security-critical code that a…

Recursos

Further reading

Listo cuando tú lo estés

Deja de pagar por desarrollador.
Empieza a cerrar el bucle.

Plexicus es el ASPM nativo de IA que escanea, filtra, corrige, pentestea y explica — de forma autónoma. Desarrolladores ilimitados, repos ilimitados, acciones de IA de uso justo. Nivel gratuito real, €269/mo anual cuando estés listo.

Comenzar gratis Reservar una demo