Use of Hard-coded, Security-relevant Constants
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 reviews.
Hard-coded values make code harder to understand and maintain. When security-relevant values are hard-coded, it increases the risk of errors when the code needs to be modified.
So behebst du diese Schwachstelle
Präventionsstrategien für Hardcoded Security Constants basierend auf 2 Shoulder-Erkennungsregeln.
Use environment variables for URLs with localhost as a development fallback
- const API_URL = 'http://localhost:3000'; + const API_URL = process.env.API_URL || 'http://localhost:3000'; const response = await fetch(`${API_URL}/users`);
Load URLs from environment variables with localhost as the development fallback
- API_URL = "http://localhost:3000/api" - DB_HOST = "127.0.0.1" + import os + + API_URL = os.getenv('API_URL', 'http://localhost:3000/api') + DB_HOST = os.getenv('DB_HOST', 'localhost') def fetch_data(): response = requests.get(f'{API_URL}/data') return response.json()
Wichtige Praktiken
- Use environment variables
- configurable via environment variables
Finden Sie Schwachstellen in Ihrem Code
Verwenden Sie Shoulder, um Ihren Code nach Use of Hard-coded, Security-relevant Constants-Mustern zu scannen. 2 Regeln.
# Scan with Shoulder CLI npx @shoulderdev/cli trust --cwe=547 # Or scan entire project npx @shoulderdev/cli trust .
Erkennungsregeln (2)
Worauf bei Code-Reviews zu achten ist
Diese Muster weisen auf potenzielle Use of Hard-coded, Security-relevant Constants-Schwachstellen hin. Achten Sie bei Code-Reviews und Sicherheitsaudits darauf.
Scanne deine Codebasis nach Use of Hard-coded, Security-relevant Constants
Shoulder CLI findet anfällige Muster in deiner gesamten Codebasis.