[GH-ISSUE #1781] (UPSTREAM) MeshCentral Security Vunlerability when version <1.1.20 #3052

Closed
opened 2026-03-14 06:22:30 +03:00 by kerem · 2 comments
Owner

Originally created by @LPJon on GitHub (Mar 4, 2024).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1781

@wh1te909 Just reporting to make you aware that there has been a securty vulnerability reported for Meshcentral servers which are less than version 1.1.20. The link below will take you to the vulnerability explanation. I will note that I successfully manually updated Meshcentral myself to version 1.1.21 already but most users probably won't do that.

Here is the link:
MeshCentral cross-site websocket hijacking (CSWSH) vulnerability

A possible breach has already been detected a few days ago and that link can be found here:
"Accepted password for undefined" #5870

Originally created by @LPJon on GitHub (Mar 4, 2024). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/1781 @wh1te909 Just reporting to make you aware that there has been a securty vulnerability reported for Meshcentral servers which are less than version 1.1.20. The link below will take you to the vulnerability explanation. I will note that I successfully manually updated Meshcentral myself to version 1.1.21 already but most users probably won't do that. Here is the link: [MeshCentral cross-site websocket hijacking (CSWSH) vulnerability](https://github.com/Ylianst/MeshCentral/security/advisories/GHSA-cp68-qrhr-g9h8) A possible breach has already been detected a few days ago and that link can be found here: [ "Accepted password for undefined" #5870 ](https://github.com/Ylianst/MeshCentral/issues/5870)
kerem closed this issue 2026-03-14 06:22:35 +03:00
Author
Owner

@wh1te909 commented on GitHub (Mar 4, 2024):

I am aware, and this isn't the place to report security vulns, please see our security policy I have already tested mesh version 1.1.21 and it will be in the next release. The mesh security vuln is not easily exploitable (requires the attacker to hijack a subdomain you own). The issue you linked about undefined user has nothing to do with the mesh vuln.

<!-- gh-comment-id:1975530178 --> @wh1te909 commented on GitHub (Mar 4, 2024): I am aware, and this isn't the place to report security vulns, please see our [security policy](https://github.com/amidaware/tacticalrmm/blob/develop/SECURITY.md) I have already tested mesh version 1.1.21 and it will be in the next release. The mesh security vuln is not easily exploitable (requires the attacker to hijack a subdomain you own). The issue you linked about undefined user has nothing to do with the mesh vuln.
Author
Owner

@LPJon commented on GitHub (Mar 4, 2024):

@wh1te909 Umm.....that was my bad. Sorry for incorrectly reporting this. I was in a hurry and didn't look.

<!-- gh-comment-id:1975797405 --> @LPJon commented on GitHub (Mar 4, 2024): @wh1te909 Umm.....that was my bad. Sorry for incorrectly reporting this. I was in a hurry and didn't look.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/tacticalrmm#3052
No description provided.