CWE-547: Use of Hard-coded, Security-relevant Constants
low-riskThe 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.
Abstraction: Base
Common Consequences
Other
→
Varies by Context
Detection Methods
Automated Static Analysis
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.)
Real-World Examples (7)
| CVE | CVSS | EPSS | KEV |
|---|---|---|---|
| CVE-2019-14837 | 9.1 | 1.0% | — |
| CVE-2023-1712 | 9.8 | 0.5% | — |
| CVE-2024-39888 | 7.5 | 0.2% | — |
| CVE-2025-30206 | 9.8 | 0.1% | — |
| CVE-2025-23253 | 2.5 | 0.1% | — |
| CVE-2026-28256 | 9.8 | 0.1% | — |
| CVE-2024-32021 | 3.9 | 0.0% | — |
0
/ 100
low-risk
Active Threat
0/50 · Minimal
Exploit Availability
0/50 · Minimal