Bugreader
Loading post ...

Hello Community !

This issue was found  a year ago in Workplace by Facebook but Marked as informative , I didn't share this write-up since it can be abused (despite if it has a low security impact or not)and once I noticed that the team fixed it I decided to share it . 

Note : it's logical issue and I didn't use any tool for doing it .

What is Facebook Workplace

Workplace is a communication tool that connects everyone in your company, even if they’re working remotely. Use familiar features like Groups, Chat, Rooms and Live video broadcasting to get people talking and working together.  

Registration 

In 2018  , the registration in workplace was opened only for business emails ( e.g. @semicolonlb.net ) so any personal email  (e.g gmail.com , hotmail.com )   wasn't allowed to register into workplace . 

Workplace Admin panel 

if you register  via your  business email( e.g [email protected]) and you verify that you own this domain , you'll be able to access the admin panel of your workplace domain and start managing your workplace that belongs to your company .

  

I started looking at the admin panel, and noticed that once you add a new user to your company you can  claimed it manually , and there is an option to deactivate this account , once you deactivate it he will not be able to register via his business email again , and a message appeared that he should contact his Workplace representative . 

 

An idea come to my mind , what if I can add  a user with another business  email that's not belong to my business domain and then deactivate this user ? 

for example I own semicolonlb.net,  can I add a new user to my company  that's belong to Facebook company fb.com ?

Unfortunately NO! 

A message will appear that this  person can't be invited as they're in another workplace. 

This message doesn't mean that this email is registered in another workplace  , but it means that any email belongs to this domain isn't allowed since it's registered on workplace  .

I tried to add an email that belongs to another business email , but this business email domain has no record in workplace ( means that no one has registered  in workplace with this domain ). let's say an email belongs to an employee in abc.com , and since no one has registered in workplace with this domain I was able to add him  in semicolonlb.net workplace admin panel .

What was the security issue here? 

The scenario that I reported it in 2018 was : 

Prevent employees of an organization from joining workplace by banning their emails before joining their organization into the workplace by Facebook.  

let's say someone from another company wants to ban [email protected]  from registering into Workplace , taking into consideration that semicolonlb.net hasn't registered yet in workplace( no email belongs to semicolon is registered yet ) ,  the attacker  will follow these steps on his admin panel to ban [email protected]

After adding the victim , deactivate this user 

Once the victim wants to register into workplace he will see this message (Account closed ) , and he can't recover his email to re-register  ( I tried forget password flow and didn't work ) , so this email got banned forever . 

if someone from semicolonlb.net registered after banning [email protected] attacker  can't reproduce the same scenario with another email  ( since semicolonlb.net has a record in workplace ) and then attacker will not be able to add any email belongs to semicolonlb.net into his admin panel . 

NOTE : After banning [email protected]  I registered in workplace via semicolon domain and I verified it to get access to the admin panel , so I tried if the admin of semicolon can recover the email admin  and found that we can't ..

so only attacker can unban [email protected]

this is the message if we try to add [email protected] into semicolon admin panel 

I reported it to Facebook,  they triaged it and  closed it  later as informative 

 Thanks for the submission. After chatting with the Workplace team, I've confirmed they are already aware of this behavior. The risk here is mitigated somewhat by the fact that people cannot provision users with domains that have been registered by another company. Of course, if this is done before a company is on Workplace that won't be prevented. However in that case the company could always reach out to our support team to handle cases like this.Given that, we don't feel that this behavior poses a significant privacy or security risk and would not qualify under our program.  

Report Re-opened

After 1 year ( 13 APRIL 2019 ) , I noticed that the  Workplace is now opened for personal email , means that anyone is able to register into workplace without using a business email , so you can use your gmail , hotmail account .

I remembered this report ! and decide to test if I can ban any personal email from registering into workplace ! I followed the same steps above and found that I can always ban any personal email  ( if the email by itself isn't registered yet despite on the domain ) and found that I can! 

I re-opened the report and sending the new information , Facebook asked me to submit a new report if I believe that there is a security issue here .

Report triaged again , and closed later with this reply : 

After consulting the Workplace product team, we have confirmed that they are already aware of the behaviour you describe in this report also. We use rate limiting as one of several controls in place to detect and prevent potential large-scale abuse here. In the case of people who sign up to Workplace with a personal email address (i.e. gmail.com or outlook.com), they can always sign up with an alias or secondary email account. If this is not possible or otherwise poses a significant blocker in their evaluation of Workplace, they can always reach out to Workplace Support to provision an evaluation environment.

My Opinion 

I respect Facebook decision, but I didn't get satisfied by this reply , despite it has a low security impact or not , but  a product that belongs to Facebook shouldn't accept behavior like this ! Anyone is able to ban any personal email ? :-(  .... ok I agree that someone can register with an alias  but in your opinion the normal users are all of them aware about aliases emails ? :-)   , and I think any user has the right to use his personal email to register in any website without creating a new one !

Imagine you wants to register in Facebook with your personal email , and suddenly you'll see this message without any reason !

Again I respect their decision and since they are aware of this behavior I didn't re-open the report and decide to not to share this report until they fixed it . 

Patching

2 weeks ago , I noticed  that this issue was fixed by allowing any email from registering even if someone from another workplace has deactivated it  ( and this is the normal behavior ).  

Timeline 

=========

Report Sent:  Tuesday, September 18, 2018 at 3:32 AM

Pre-triage: Thursday, September 20, 2018 at 10:19 PM

Triaged : Saturday, September 22, 2018 at 12:10 AM

Closed as informative :  Wednesday, October 24, 2018 at 6:56 PM

Re-opened : Saturday, April 13, 2019 at 4:09 PM 

Facebook asked to submit a new report  :  Friday, January 31, 2020 at 12:13 AM

Submitting new report :  Saturday, February 1, 2020 at 6:38 PM  

Facebook asked for new details :  Friday, February 7, 2020 at 4:56 PM  

  Thanks for writing in.I understand that you have submitted this report as a follow-up to #------------- . To help us investigate this further, I have a couple of questions:- Are you able to disable registration for all personal email addresses with a particular domain, or just for a single email address?- Can the victim use the password reset or account recovery flows to regain access and create a new Workplace account?

Replying  Friday, February 7, 2020 at 7:58 PM

Pre-triaged : Monday, February 17, 2020 at 5:42 PM

Closed as informative :  Tuesday, February 18, 2020 at 5:51 PM

Thanks for your patience here.After consulting the Workplace product team, we have confirmed that they are already aware of the behaviour you describe in this report also. We use rate limiting as one of several controls in place to detect and prevent potential large-scale abuse here.In the case of people who sign up to Workplace with a personal email address (i.e. gmail.com or outlook.com), they can always sign up with an alias or secondary email account. If this is not possible or otherwise poses a significant blocker in their evaluation of Workplace, they can always reach out to Workplace Support to provision an evaluation environment.