Comments on: WRITE UP – TWITTER BUG BOUNTY [Report of my 1st bugbounty]: “POODLE SSLv3 bug on multiple twitter smtp servers” /write-up-twitter-bug-bounty-my-1st-bugbounty-poodle-sslv3-bug-on-multiple-twitter-smtp-servers/ just another security blog. Sat, 08 Jan 2022 00:33:20 +0000 hourly 1 https://wordpress.org/?v=5.9.3 By: Aniket Bhutani /write-up-twitter-bug-bounty-my-1st-bugbounty-poodle-sslv3-bug-on-multiple-twitter-smtp-servers/#comment-6585 Sun, 19 Jul 2020 15:32:12 +0000 http://e02.omespino.com/?p=225#comment-6585 Hi Omespino,

I am trying to use the same dork for Twitter and as well as for other targets, but not getting results.
I am getting “No results Found”

]]> By: omespino /write-up-twitter-bug-bounty-my-1st-bugbounty-poodle-sslv3-bug-on-multiple-twitter-smtp-servers/#comment-5835 Fri, 06 Sep 2019 22:09:15 +0000 http://e02.omespino.com/?p=225#comment-5835 In reply to Afolic.

Hey thanks for reading, I just stopped and reported after I founded that servers, the twitter team does not requiered any poc, here is the original report for reference https://hackerone.com/reports/288966

]]> By: Afolic /write-up-twitter-bug-bounty-my-1st-bugbounty-poodle-sslv3-bug-on-multiple-twitter-smtp-servers/#comment-5814 Sun, 01 Sep 2019 23:20:21 +0000 http://e02.omespino.com/?p=225#comment-5814 Cool find, did you probe further after this or you just stopped here and reported it straight away?

]]>