> 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/business-logic/inconsistent-management-of-exceptional-entries.md).
# Inconsistent Management of Exceptional Entries
Inconsistent Management of Exceptional Entries notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Inconsistent Handling of Exceptional Input
**Description of lab**
This lab shows poor validation of user inputs in the registration process. This logical flaw allows access to administrative features normally reserved for employees. / Purpose: to access the administration panel and delete user **carlos**.
**Observation initiale**
Upon registration, a validation email is sent to the address provided. / The operating server receives \*\* all emails\*\* associated with the domain and its subdomains:
```bash
@exploit-0a8c00a504628ac58246f51601c6009c.exploit-server.net
```
Thus, any address created with this domain or its subdomains is admissible.
**Identified abnormal behaviour**
By creating an email address containing a very large number of characters before the `@` symbol, we find that the field \*\*
{% code overflow="wrap" %}
```bash
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA@exploit-0a8c00a504628ac58246f51601c6009c.exploit-server.net
```
{% endcode %}
This limit causes an inconsistency between the value actually stored and that displayed or used for security checks.
**Operation of the fault**
The goal is to force truncation so that the registered email ends exactly with the `dontwannacry.com` confidence area.
Length verification:
{% code overflow="wrap" %}
```bash
eecho -n "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA@dontwannacry.com" | wc -c
```
{% endcode %}
Once the 255 characters have been reached, the final address is constructed in this way:
{% code overflow="wrap" %}
```bash
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA@dontwannacry.com.exploit-0a8c00a504628ac58246f51601c6009c.exploit-server.net
```
{% endcode %}
The operating server receives the email well, as it accepts all subdomains.
The application, after truncation, interprets the address as belonging to the `dontwannacry.com` domain.
The account is considered to be internal or trustworthy. / Once connected, access to the **Administration Board** is allowed without additional control.
---
# 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/business-logic/inconsistent-management-of-exceptional-entries.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.
