RINGOTEL Major hack

pbxgeek

Well-Known Member
Jan 19, 2021
1,025
342
83
39
Immediate attention is needed from all Ringotel users. Ringotel has confirmed it was hacked and that all credentials were leaked. I recommend immediately rotating all SIP passwords, Ringotel app login credentials, API keys, and API keys for any external integrations you set up in Ringotel.

Below is the email that was sent to everyone.

1795360930995.png
 
Hi,

We are still working out the right order of steps after the Ringotel breach and have only tested on a few extensions, so I'd like your advice at each step. I read the current master code, so my assumptions may not match v2.2.2.

STEP 1: THE API TOKEN
1a. We rotated the Ringotel API key and entered it with the API Token button (Default Settings, mobile_apps / ringotel_api_token). Is that the only place FS PBX stores it?
1b. Is the token encrypted at rest in Default Settings?
1c. Do any queued or failed jobs in the ringotel queue keep using the old token?

STEP 2: THE WEBHOOK
2a. The webhook check compares the request's api_key with the same API token, using ===. Is the API key meant to double as the webhook secret?
2b. If the token is ever empty, would a request with no api_key pass (null === null)?
2c. Could we have a separate webhook secret, and a constant-time comparison (hash_equals)?
2d. Is there a way to switch off the webhook and the Ringotel jobs quickly during an incident?

STEP 3: SIP PASSWORDS
3a. After we reset an extension's SIP password in FS PBX, what is the correct way to send it to Ringotel? Is Deactivate then Activate the only way (it calls updateUser with the extension password)?
3b. What does Reset password in the extension's mobile app tab do? It sends only the user and org IDs to resetUserPassword. Does it change the SIP password, or only the app login?
3c. Is there, or could there be, a bulk action to push current passwords to Ringotel for a whole domain?
3d. Existing registrations stay up after a password change. Is there a way in FS PBX to force them to re-register, or should we flush them with fs_cli?

STEP 4: THE ACL
4a. Ringotel's server IPs are in our rfc1918 ACL (allow, otherwise deny). Is that there for NAT handling, or does it let calls in without SIP authentication? Which sip profile settings use it?
4b. Does Ringotel need an ACL entry at all, or can it work with credentials only?
4c. If the entry must stay, what is the safest setup? For example, only the regions we use, per-extension call limits and international blocks.
4d. How should we search the CDRs for calls that came from Ringotel's IPs since Nov 20?
 
Here is the procedure that needs to be done:
1) update Ringotel API KEY in their portal and then update it in the Pbx
2) identify all uses who has Ringotel apps.
3) classify them into 2 categories: users with only mobile apps and users with both mobile apps and physical phones
4) make sure you are on the latest FS PBX version
5) reset sip password for all users with mobile apps only
6) restart the phone and 5 seconds later change the password for all users that have mobile apps and physical phones. This will make sure that the phone will restart and download the new sip password
 
  • Like
Reactions: marc8lange
Resetting the SIP password pushes the new SIP password to Ringotel on the latest version. So it's important to update.
We have a bulk action for Ringotel app password credential resets.
Ringotel app password and SIP password are different and should be treated differently. Both should be reset as a precaution.