According to SOAR [REF-1479], the following detection techniques may be useful: ``` Highly cost effective: ``` Bytecode Weakness Analysis - including disassembler + source code weakness analysis Binary Weakness Analysis - including disassembler + source code weakness analysis ``` Cost effective for partial coverage: ``` Binary / Bytecode Quality Analysis Binary / Bytecode simple extractor - strings, ELF readers, etc.
CWE-676 Base Borrador
Use of Potentially Dangerous Function
This vulnerability occurs when code calls a function that can be dangerous if misused, but can also be used safely with proper precautions. The risk lies not in the function itself, but in how it's…
Definición
What is CWE-676?
This vulnerability occurs when code calls a function that can be dangerous if misused, but can also be used safely with proper precautions. The risk lies not in the function itself, but in how it's implemented.
Many programming languages and libraries include powerful, low-level functions that offer performance benefits or direct system access. Functions like `strcpy()`, `eval()`, or `system()` are common examples. While they are legitimate tools, they become security risks when developers use them without validating input, managing memory, or understanding their side effects. The core issue is assuming these functions are safe by default, rather than treating them as operations that require explicit safeguards.
To mitigate this, developers should first seek safer, modern alternatives provided by the language or framework, such as bounded string copy functions or secure APIs. When a dangerous function must be used, it is critical to implement strict input validation, output encoding, and context-aware sanitization around it. Security is maintained by wrapping these functions with robust checks and limits, never trusting uncontrolled data, and conducting regular code reviews focused on these specific high-risk calls.
Impacto en el mundo real
Real-world CVEs caused by CWE-676
-
Library has multiple buffer overflows using sprintf() and strcpy()
-
Buffer overflow using strcat()
-
Buffer overflow using strcpy()
-
Buffer overflow using strcpy()
-
Vulnerable use of strcpy() changed to use safer strlcpy()
-
Buffer overflow using strcpy()
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 C
The following code attempts to create a local copy of a buffer to perform some manipulations to the data.
void manipulate_string(char * string){
char buf[24];
strcpy(buf, string);
...
} 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-676
- Build and Compilation / Implementation Identify a list of prohibited API functions and prohibit developers from using these functions, providing safer alternatives. In some cases, automatic code analysis tools or the compiler can be instructed to spot use of prohibited functions, such as the "banned.h" include file from Microsoft's SDL. [REF-554] [REF-7]
Señales de detección
How to detect CWE-676
According to SOAR [REF-1479], the following detection techniques may be useful: ``` Cost effective for partial coverage: ``` Binary / Bytecode disassembler - then use manual analysis for vulnerabilities & anomalies
According to SOAR [REF-1479], the following detection techniques may be useful: ``` Highly cost effective: ``` Debugger ``` Cost effective for partial coverage: ``` Monitored Virtual Environment - run potentially malicious code in sandbox / wrapper / virtual machine, see if it does anything suspicious
According to SOAR [REF-1479], the following detection techniques may be useful: ``` Highly cost effective: ``` Manual Source Code Review (not inspections) ``` Cost effective for partial coverage: ``` Focused Manual Spotcheck - Focused manual analysis of source
According to SOAR [REF-1479], the following detection techniques may be useful: ``` Highly cost effective: ``` Source code Weakness Analyzer Context-configured Source Code Weakness Analyzer ``` Cost effective for partial coverage: ``` Warning Flags Source Code Quality Analyzer
According to SOAR [REF-1479], the following detection techniques may be useful: ``` Cost effective for partial coverage: ``` Origin Analysis
CWE-676
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-676?
¿Qué gravedad tiene CWE-676?
¿Qué lenguajes o plataformas se ven afectados por CWE-676?
¿Cómo puedo prevenir CWE-676?
¿Cómo detecta y corrige Plexicus CWE-676?
¿Dónde puedo aprender más sobre CWE-676?
Frequently asked questions
¿Qué es CWE-676?
This vulnerability occurs when code calls a function that can be dangerous if misused, but can also be used safely with proper precautions. The risk lies not in the function itself, but in how it's implemented.
¿Qué gravedad tiene CWE-676?
MITRE califica la probabilidad de explotación como Alta — esta debilidad se explota activamente en la práctica y debe priorizarse para su remediación.
¿Qué lenguajes o plataformas se ven afectados por CWE-676?
MITRE lists the following affected platforms: C, C++.
¿Cómo puedo prevenir CWE-676?
Identify a list of prohibited API functions and prohibit developers from using these functions, providing safer alternatives. In some cases, automatic code analysis tools or the compiler can be instructed to spot use of prohibited functions, such as the "banned.h" include file from Microsoft's SDL. [REF-554] [REF-7]
¿Cómo detecta y corrige Plexicus CWE-676?
El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-676 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-676?
MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/676.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.
Debilidades relacionadas
Weaknesses related to CWE-676
CWE-1177 Padre
Use of Prohibited Code
This vulnerability occurs when software incorporates a function, library, or third-party component that has been explicitly banned by the…
CWE-242 Hermano
Use of Inherently Dangerous Function
This vulnerability occurs when code uses functions that are inherently unsafe and cannot be reliably secured, posing a direct risk to…
CWE-785 Hijo
Use of Path Manipulation Function without Maximum-sized Buffer
This vulnerability occurs when a program uses a path manipulation function but supplies an output buffer that is too small to hold the…
Recursos
Further reading
- MITRE — CWE-676 oficial https://cwe.mitre.org/data/definitions/676.html
- Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors https://samate.nist.gov/SSATTM_Content/papers/Seven%20Pernicious%20Kingdoms%20-%20Taxonomy%20of%20Sw%20Security%20Errors%20-%20Tsipenyuk%20-%20Chess%20-%20McGraw.pdf
- Security Development Lifecycle (SDL) Banned Function Calls https://learn.microsoft.com/en-us/previous-versions/bb288454(v=msdn.10)?redirectedfrom=MSDN
- Writing Secure Code https://www.microsoftpressstore.com/store/writing-secure-code-9780735617223
- State-of-the-Art Resources (SOAR) for Software Vulnerability Detection, Test, and Evaluation https://www.ida.org/-/media/feature/publications/s/st/stateoftheart-resources-soar-for-software-vulnerability-detection-test-and-evaluation/p-5061.ashx
¿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.