> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/web/information-disclosure/information-disclosure-via-version-control-history.md).
# Information Disclosure via Version Control History
Information Disclosure via Version Control History notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Information Disclosure in Version Control History
**Description of lab**
This lab exposes sensitive information through the history of a version control repository. / The goal is to retrieve the user's password **administrator**, then log in with this account to delete user **carlos**.
**Initial analysis**
By exploring the application, we see the presence of a directory **`.git`** accessible directly from the web server.
This indicates that the complete Git repository is publicly displayed, potentially enabling the source and history of the changes to be retrieved.
**Exploitation**
**Git Repository Extraction**/ The git-dumper tool is used to download the contents of the `.git` directory:
```bash
git-dumper https://0a7800030384626580b39ee5001e00b1.web-security-academy.net/.git .git
```
**Analysis of commit history**/ Once the repository has been reconstructed locally, the history of the commit is consulted:
```bash
git log
```
The analysis reveals that a commit contains the removal of an administrator password.
**Inspection of differences**/ The exact content of this commit is reviewed to identify the deleted information:
```bash
git log -p ab875bcd9cf3ea84ad6af9471521aea4c3a1852d
```
The differences displayed make it possible to find the user's password **administrator**.
* q0b3xu3ko6pqcqdjofrq
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hacking-notes.jord4n.pro/web/information-disclosure/information-disclosure-via-version-control-history.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)