# Open Signups

#### Description:

In case signups are not turned off, any user can create an account on the Jenkins instance and gain (privileged) access to (internal) developer resources.

#### Testing:

Navigate to one of the following app routes and check if signups are enabled:

```
/signup
/jenkins/signup
```

#### Remediation:

Make sure to disable signups for Jenkins. You can easily do so by:

1. Navigate to **Configure Global Security** page over at `/configureSecurity`
2. And make sure that the option **Allow users to signup** is disabled
3. Finally, **Apply** and **Save** your changes

<figure><img src="/files/ZzmB227KqJ3C8SrJZ2LV" alt=""><figcaption></figcaption></figure>

#### Potential Impact:

Unauthorized users are able to create an account, this often introduces no potential risk.\
\
However, if the in-app permissions are not set and give newly signed up users too much privileges, it could result in a new attack vector.\
\
This could introduce several new security anomalies to your company (especially code execution as Jenkins CI/CD tool).

#### References:

* <https://rohit-soni.medium.com/chaining-multiple-vulnerabilities-leads-to-remote-code-execution-rce-on-paytm-e77f2fd2295e>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://bugology.intigriti.io/misconfig-mapper-docs/services/jenkins/open-signups.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.