# CVE-2023-36081

### <mark style="color:yellow;">**Description**</mark>&#x20;

Stored Cross-Site Scripting vulnerability in GatesAIr Flexiva FM Transmitter/Exciter v.FAX 150W leads to execute JS arbitrary code and application lockout via a crafted script to the web application dashboard.

**Discoverer: Eslam Kamal (Strik3r)**&#x20;

**Vendor of Product: GatesAIr**&#x20;

**Affected Product: FM Transmitter/Exciter v.FAX 150W**&#x20;

### <mark style="color:yellow;">Introduction</mark>

Stored Cross-site Scripting (XSS) is the most dangerous type of Cross Site Scripting. Web applications that allow users to store data are potentially exposed to this type of attack. Stored XSS occurs when a web application gathers input from a user which might be malicious, and then stores that input in a data store for later use.

### <mark style="color:yellow;">Details</mark>

During the test, we found that the "System Service Settings" endpoint's input field doesn't check or validate the input before processing it to the back-end which leads to Stored-XSS and also leads to Lockout the whole Application to all users.

If we tried to inject any XSS payloads within all of these fields the Front-end will prevent us of doing that as shown below:

<figure><img src="https://2341258708-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNXCJWNoU0PexwJ6yBpmG%2Fuploads%2FsIqPyBwFIA8SdUSumfgN%2Fimage.png?alt=media&#x26;token=c7b9cbc2-c4a3-417e-ac61-898786159787" alt=""><figcaption></figcaption></figure>

So, to bypass the Front-end restriction we will use BurpSuit to capture this update request and send our Malformed payload to the back-end:

<figure><img src="https://2341258708-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNXCJWNoU0PexwJ6yBpmG%2Fuploads%2F7BcyF22vOfTzkVqrjMZf%2Fimage.png?alt=media&#x26;token=fa3e04ec-395d-4970-be1b-eb0dc8604c8a" alt=""><figcaption></figcaption></figure>

As you can see above our payload send successfully to the back-end, and will notice that our payload fired at the whole application, Because we injected this payload at the device Title. and because this is shown within the Application, the payload will always work when entering the application.

<figure><img src="https://2341258708-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNXCJWNoU0PexwJ6yBpmG%2Fuploads%2FyemqzVjYzggChb5tz95Z%2Fimage.png?alt=media&#x26;token=14da9e58-746c-4317-8327-e907a08443a3" alt=""><figcaption></figcaption></figure>

What also happened with this payload injected into the application back-end is that other fields within the application's data were affected with the same payload and malformed the back-end "HTML" (Server Version)

<figure><img src="https://2341258708-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNXCJWNoU0PexwJ6yBpmG%2Fuploads%2FhO445X6xll5pgzadt3Qn%2Fimage.png?alt=media&#x26;token=e9fb0983-bee0-4e12-aaa9-7320a8c1e2e3" alt=""><figcaption></figcaption></figure>

This warning will keep all legitimate users out of the applications because of the malformed HTML  the application won\`t be able to load normally.

to verify this, you can notice that at the /json endpoint the "htmlGUIVersion" has been infected with our XSS payload as well as the "pagetitle"&#x20;

<figure><img src="https://2341258708-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FNXCJWNoU0PexwJ6yBpmG%2Fuploads%2FivVDuT3OVUGfwoUUH3ty%2Fimage.png?alt=media&#x26;token=a9e3c117-82ac-4fce-b7ab-1fd5b084ca5a" alt=""><figcaption></figcaption></figure>





