HexBrain

X / xAI · Report #273698

Unauthorized Access to Protected Tweets via niche.co API

Validstatus
highseverity
22upvotes
2 Nov 2017disclosed

How it was found

Hello,

Summary: Normally If user (victim) set to private / protect their tweets in setting Tweet privacy, other people/user will not able to see their recent or their pass status/twits when they visit his/her (victim) profile. people only can see their (victim) profile images and information about how many tweet already post by that user , how many followers and following by that account and how many likes etc etc. but i found a way to view the protected tweets from other user who protect their tweets.

Description: in your policy i see there is new domain add as in scope target , and the domain is niche.co . there is some condition needed to success reproduce this vulnerability:

  1. the victim need to connect their twitter account with niche.co
  2. use the niche.co API to Access the Protected Tweets

Steps To Reproduce:

victim side

  • victim account is https://twitter.com/dummysystems
  • lets say the victim already set to protect his/her tweets via https://twitter.com/settings/safety {F225673}
  • now when other user try to visit victim profile it will look like this {F225670}
  • now visit https://www.niche.co/get-started and chose twitter , allow and or Authorize Niche to use your account and complete the rest (including confirming your email address).

attacker side

  1. attacker no need to have twitter account and or no need to have Niche account here , this made the severity is high
  2. just visit https://www.niche.co/api/v1/users/[victim_twitter_account] ( in this case the victim is https://www.niche.co/api/v1/users/dummysystems , the attacker will show some important information disclosure regarding the victim account {F225668}
  3. scroll down the page till you see something like this /users/52667/posts?accounts=162059 {F225669}
  4. and open it, so the full URI will become https://www.niche.co/api/v1//users/52667/posts?accounts=162059
  5. and BOOM! the attacker now have Access to Protected Tweets from victim account. {F225671} {F225672}

noted to follow the rules, I use my own account as the victim, so there is no other / real account has been compromised.

Regards,

This report was disclosed publicly on HackerOne and belongs to its author and the program. See the original