Skip to main content
HighContentOWASP A05:2021CWE-538

How to fix: .git Directory Paths Exposed

.git directory paths found in page source.

Why it matters

Exposed .git allows downloading entire source code history.

If .git is accessible, attackers can reconstruct your entire repository.

How to fix it

  1. 1Block access to .git directory in web server config.

Code examples

Block access to .git directory

nginx
# Block .git and other VCS directories
location ~ /\.git {
  deny all;
  return 404;
}

# Apache:
# <DirectoryMatch "^\.git">
#   Require all denied
# </DirectoryMatch>

References

Detected automatically by VulnRadar. The check id is git-directory-exposed, stable across every scan so you can filter or diff on it.

See every content check

Questions

How severe is .git Directory Paths Exposed?
VulnRadar rates this high 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 git-directory-exposed, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does .git Directory Paths Exposed 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.

Propose a checkHow a check is built

Scan your own site for .git directory paths exposed

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: .git Directory Paths Exposed | VulnRadar