Incorrect Behavior Make Crash and Can not Access Account in polonel/trudesk
May 25th 2022
Incorrect Behavior Make Crash and Can not Access Account
Proof of Concept
1. Send a test message and get the request, send it to Repeater 2. Replace the value of owner and cId with the id of two victims 3. Send the request
- Make victim's account crash
- Victim can not access the account after although clear the browsing data
- Dangerous to all users
- Update: The admin account also crashed !
You marked the affected version as "the last version" but in your POC it is using docker.trudesk.io which is using a different codebase.
Please test on version 1.2.2 as the demo version is being decommissioned at the end of the month. You will need to download and run the software locally. Please refer to the documentation.
Hi! I am sorry for my bad! I tested on the version 1.2.2, this vulnerability still occurring! This is my new POC video: https://drive.google.com/file/d/1Hx2ZNXqGD6yVYGmH8nDBs7sG0iERGbbx/view?usp=sharing Thank you so much !!!
I'm not able to reproduce. I'm getting a 400 Bad Request error when changing the
cId to a user's id. This is because it cannot find a conversation with that ID.
In the POC you do not show that the IDs you have stored in the notepad are actual user IDs.
If you change the
owner field in the payload and the conversation id is valid it just shows that another user was part of the conversation.
Can you please show where the IDs you have in notepad came from so I can try to reproduce with the same steps?
@researcher I also want to confirm if you see ALL the user IDs when logged into a non-admin account and verify if you can reproduce the vulnerability with a regular user as the attacker instead of an admin as the attacker.
Hi Chris Brame, I get the ID of user victim from the URL in message page of Attacker's account, you can see it in this full POC video
confirm: see ALL the user IDs when logged into a non-admin account:
Those IDs in the last video and the IDs in the URL are the conversations IDs, NOT the user IDs.
I think that is the cause of the crash is the user ID is missing validation when you replace it with a conversation ID.
But this did help me, I will try to reproduce and update this report when I can.
Can you update using the
develop branch and see if the exploit is still working? I can not reproduce but I did change some other things with messages which may have fixed this at the same time.
If it is fixed on the
develop branch I will stash my code and test again on
Hi @Chris Brame, I updated using the
develop branch with docker-compose:
docker-compose up -d
I tested again. The exploit is still working.
Is there something wrong?
That would have not been updated as I didn't update the docker images.
I have updated the docker image for the
next tag. You will need to change the
docker-compose file to use the
Hi @maintainer ! I tested again using the
develop branch. The vulnerability fixed! You can watch this video:
I have marked this as valid as I believe it was fixed in a commit that will release in v1.2.3
@researcher Thanks for your assistance and multiple testing of the application.
@admin Can you change the affected version of this report to be