Hardcoded URL
ID |
url |
Severity |
info |
Vendor |
- |
Family |
url |
Security
A URL could contain sensitive information. If this is the case, the attacker could use this for malicious purposes.
Mitigation / Fix
-
Remove the URL from the source code or committed file.
-
Follow your policy for handling leaked secrets, which typically require revoking the secret in the target system(s).
-
If under a git repository, you may remove unwanted files from the repository history using tools like
git filter-repo
orBFG Repo-Cleaner
. You may follow the procedure listed here for GitHub.
You should consider any sensitive data in commits with secrets as compromised. Remember that secrets may be removed from history in your projects, but not in other users' cloned or forked repositories. |
-
Check access logs to ensure that the secret was not used by unintended actors during the compromised period.