How to fix: Configuration file reference detected in links/assets
The page contains an href/src/action link to a configuration filename (config.yaml, config.json, .env, docker-compose) that often indicates server-side configuration files.
Why it matters
References to sensitive configuration may indicate they are exposed at the URL mentioned.
When a page surfaces the names of server-side configuration files, it provides a roadmap for an attacker probing for common misconfiguration paths.
How to fix it
- 1Verify that the referenced paths (e.g. /config.yaml, /.env, /docker-compose.yml) return 404 on the public origin.
- 2Block access to dotfiles and config files at the reverse proxy (location ~ /\. { deny all; }).
- 3Remove in-content references unless they are user-facing documentation.
- 4If these are documentation pages, ensure they are noindexed and not advertised in the sitemap.
Code examples
Block config file access via web server
# Block common config file extensions
location ~* \.(conf|config|cfg|ini|yaml|yml|toml|json)$ {
deny all;
return 404;
}
# Ensure web root does not include application config directoryReferences
Detected automatically by VulnRadar. The check id is config-file-leaked, stable across every scan so you can filter or diff on it.
More content checks
- MediumPotential Open Redirect Parameters
- HighDirectory Listing Appears Enabled
- MediumSensitive File References Detected
- HighPotentially Outdated JavaScript Libraries
- Inforobots.txt Present - Review Manually
- InfoCMS / Technology Fingerprinting
- MediumPotentially Dangerous Inline JavaScript
- LowServer version disclosed in response header
Questions
- How severe is Configuration file reference detected in links/assets?
- VulnRadar rates this medium severity in the content category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id config-file-leaked, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Configuration file reference detected in links/assets map to?
- It maps to CWE-538. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.