Probing Exposed `.git` Repository & Admin Portal Without Consent
While browsing a public logistics portal in India, an engineering student checks whether `/.git/HEAD` is accessible. Discovering directory indexing enabled, the student reconstructs source code, extracts hardcoded staging DB credentials, and logs into an internal admin panel out of curiosity.
HTTP GET enumeration of `/.git/` objects (`git-dumper` style reconstruction), local secret parsing from `.env.bak`, and authenticated login into an administrative portal belonging to an unrelated third party.
Publicly reachable URLs or misconfigured `.git` folders do NOT grant consent to download source code or log in with recovered credentials.
- •Accessing proprietary source code and internal administrative interfaces without owner awareness.
- •Reusing discovered credentials crosses from passive observation into active intrusion.
- •Exposes unrelated third-party customer logistics records to confidentiality risk.
Civil liability (compensation) for accessing a computer resource and downloading data/source code without owner permission.
Criminal offence (up to 3 years imprisonment / ₹5 Lakh fine) if accessing or downloading recovered secrets is established to be "dishonestly or fraudulently" committed.
- Section 43 applies whenever a person accesses, downloads, or copies data from any computer system without permission of the owner or person in charge.
- Indian cyber law does not contain a blanket statutory exemption protecting curious "good-faith" login into private third-party portals without prior consent or VDP safe harbor.
In educational terms, this scenario demonstrates the "Open Door Fallacy": an unlocked file path never equals legal authorization. Even if no data is modified or deleted, merely logging in with discovered credentials transforms passive error discovery into active unauthorized access.
- ›A 200 OK HTTP response on `/.git/HEAD` proves misconfiguration without needing object reconstruction.
- ›Never authenticate into another organization’s admin portal using discovered credentials.
- Stop immediately upon noticing `.git/HEAD` exposure without downloading repository blobs or secrets.
- Check if the organization operates a `/.well-known/security.txt` or VDP; otherwise report the exposure passively via CERT-In coordination (`[email protected]`).
- Practice source-code recovery labs strictly inside isolated owned VMs or CSG Proving Grounds.