CWE-547 Base Brouillon

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…

Définition

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.

Impact réel

Real-world CVEs caused by CWE-547

Aucune référence CVE publique n'est liée à ce CWE dans le catalogue MITRE pour le moment.

Comment les attaquants l'exploitent

Parcours de l'attaquant étape par étape

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.

Exemple de code vulnérable

Vulnerable C

The following is an example of using a hard-coded constant instead of a symbolic name.

Vulnérable C

char buffer[1024];
  ...
  fgets(buffer, 1024, stdin);

Exemple de code sécurisé

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.

Sécurisé C

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.

Liste de contrôle de prévention

How to prevent CWE-547

Implementation Avoid using hard-coded constants. Configuration files offer a more flexible solution.

Signaux de détection

How to detect CWE-547

Automated Static Analysis High

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

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.

Request AI Swarm Pentest

Questions fréquentes

Frequently asked questions

Qu'est-ce que CWE-547 ?

Quelle est la gravité de CWE-547 ?

MITRE n'a pas publié de note de probabilité d'exploitation pour cette faiblesse. Traitez-la comme un impact moyen jusqu'à ce que votre modèle de menace prouve le contraire.

Quels langages ou plateformes sont affectés par CWE-547 ?

MITRE n'a pas spécifié les plateformes affectées pour ce CWE — il peut s'appliquer à la plupart des stacks applicatives.

Comment puis-je prévenir CWE-547 ?

Avoid using hard-coded constants. Configuration files offer a more flexible solution.

Comment Plexicus détecte et corrige CWE-547 ?

Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-547 à chaque commit. Lorsqu'une correspondance est trouvée, notre agent Codex Remedium ouvre une PR de correction avec le code corrigé, les tests et un résumé d'une ligne pour le relecteur.

Où puis-je en savoir plus sur CWE-547 ?

MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/547.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.

Faiblesses associées

Weaknesses related to CWE-547

CWE-1078 Parent

Prêt à valider ce qui compte.

Plexicus est Proof-Driven AppSec : findings validés, compréhension contextuelle et remédiation relue — ancrée dans la preuve, scopée avec vous.

Réserver un Pentest

Use of Hard-coded, Security-relevant Constants

What is CWE-547?

Real-world CVEs caused by CWE-547

Parcours de l'attaquant étape par étape

Vulnerable C

Secure C

How to prevent CWE-547

How to detect CWE-547

Don't catalog this weakness. Prove it's reachable.

Frequently asked questions

Weaknesses related to CWE-547

Inappropriate Source Code Style or Formatting

Invokable Control Element with Excessive Volume of Commented-out Code

Inconsistent Naming Conventions for Identifiers

Insufficient Use of Symbolic Constants

Insufficient Isolation of Symbolic Constant Definitions

Use of Same Variable for Multiple Purposes

Inappropriate Comment Style

Inappropriate Whitespace Style

Source Code Element without Standard Prologue

Further reading

Prêt à valider ce qui compte.

Vérifiez si l'AI Swarm Pentest convient à votre environnement.

Demande reçue. Réservez la prochaine étape.

Sample evidence handover

Server-Side Request Forgery in `webhooks/receiver`