Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
CWE-547 Base Borrador
Use of Hard-coded, Security-relevant Constants
This vulnerability occurs when code directly embeds security-critical values like passwords, cryptographic keys, or access levels as raw numbers or strings, instead of using named constants or…
Definición
What is CWE-547?
This vulnerability occurs when code directly embeds security-critical values like passwords, cryptographic keys, or access levels as raw numbers or strings, instead of using named constants or configuration files. This practice makes the code brittle and error-prone during updates or security reviews.
Hard-coding security values creates a maintenance nightmare. If a secret needs to be rotated or a permission level changed, developers must hunt through the entire codebase for every occurrence. Missing just one instance can introduce a security gap or break functionality. Once software is deployed, updating these embedded values often requires a full re-release, which may not even be possible in some environments.
These constants also risk exposure if the code is ever leaked or reverse-engineered, turning a simple configuration change into a major breach. While SAST tools can flag the pattern, Plexicus uses AI to not only detect these hard-coded secrets but also suggest the specific code fix—like moving the value to a secure configuration manager—saving hours of manual refactoring and reducing human error.
Impacto en el mundo real
Real-world CVEs caused by CWE-547
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-547
- Implementation Avoid using hard-coded constants. Configuration files offer a more flexible solution.
Señales de detección
How to detect CWE-547
CWE-547
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-547?
¿Qué gravedad tiene CWE-547?
¿Qué lenguajes o plataformas se ven afectados por CWE-547?
¿Cómo puedo prevenir CWE-547?
¿Cómo detecta y corrige Plexicus CWE-547?
¿Dónde puedo aprender más sobre CWE-547?
Frequently asked questions
¿Qué es CWE-547?
This vulnerability occurs when code directly embeds security-critical values like passwords, cryptographic keys, or access levels as raw numbers or strings, instead of using named constants or configuration files. This practice makes the code brittle and error-prone during updates or security reviews.
¿Qué gravedad tiene CWE-547?
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-547?
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-547?
Avoid using hard-coded constants. Configuration files offer a more flexible solution.
¿Cómo detecta y corrige Plexicus CWE-547?
El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-547 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-547?
MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/547.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.
Debilidades relacionadas
Weaknesses related to CWE-547
CWE-1078 Padre
Inappropriate Source Code Style or Formatting
This weakness occurs when source code violates established style guidelines for formatting, indentation, whitespace, or commenting, making…
CWE-1085 Hermano
Invokable Control Element with Excessive Volume of Commented-out Code
This weakness occurs when a callable function, method, or procedure contains a large amount of inactive, commented-out code within its…
CWE-1099 Hermano
Inconsistent Naming Conventions for Identifiers
This weakness occurs when a codebase uses mixed naming styles for elements like variables, functions, data types, or files, creating an…
CWE-1106 Hermano
Insufficient Use of Symbolic Constants
This weakness occurs when developers embed raw numbers or text strings directly in code instead of using named symbolic constants, making…
CWE-1107 Hermano
Insufficient Isolation of Symbolic Constant Definitions
This weakness occurs when a codebase uses symbolic constants (like named values for numbers or strings) but scatters their definitions…
CWE-1109 Hermano
Use of Same Variable for Multiple Purposes
This weakness occurs when a single variable is reused to handle multiple, unrelated tasks or to store different pieces of data throughout…
CWE-1113 Hermano
Inappropriate Comment Style
This weakness occurs when source code comments are written in a style or format that doesn't match the project's established standards or…
CWE-1114 Hermano
Inappropriate Whitespace Style
This weakness occurs when source code uses inconsistent or non-standard whitespace formatting, such as irregular indentation, spacing, or…
CWE-1115 Hermano
Source Code Element without Standard Prologue
This weakness occurs when source code files or modules lack a consistent, standardized header or prologue that the development team has…
¿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.