BaseDraft
CWE-547Use of Hard-coded, Security-relevant Constants
Category: other
Description
The product uses hard-coded constants instead of symbolic names for security-critical values, which increases the likelihood of mistakes during code maintenance or security policy change.
If the developer does not find all occurrences of the hard-coded constants, an incorrect policy decision may be made if one of the constants is not changed. Making changes to these values will require code changes that may be difficult or impossible once the system is released to the field. In addition, these hard-coded values may become available to attackers if the code is ever disclosed.
Common consequences· 1
- Other — Varies by Context, Quality Degradation, Reduce MaintainabilityThe existence of hardcoded constants could cause unexpected behavior and the introduction of weaknesses during code maintenance or when making changes to the code if all occurrences are not modified. The use of hardcoded constants is an indication of poor quality.
Potential mitigations· 1
- [Implementation]Avoid using hard-coded constants. Configuration files offer a more flexible solution.
References
(incoming)2
| Type | Target | Confidence | Tier |
|---|---|---|---|
| Vulnerability | CVE-2025-30206cve-2025-30206 | 0% | live |
| Vulnerability | CVE-2026-28256cve-2026-28256 | 0% | live |
Related by meaning· 6
Nearest entities by semantic similarity across the cs-graph corpus.