Third Party Apps Could Read Twitter Messaging

According to the company, no one used this vulnerability and the issues is now solved
18 December 2018   1052

Until the beginning of December, third-party applications could access Twitter private messages. According to the company, no one took advantage of this vulnerability. Terence Eden, who found it, was paid almost $ 3,000 under the Bug Bounty program.

In 2013, there was a leak of keys to the Twitter API - so applications could access the interface bypassing the social network. To protect users, Twitter implemented an application authorization mechanism through predefined addresses (Callback URL), but it didn’t suit everyone.

Applications that do not support Callback URLs could authenticate using PIN codes. With this authorization, a window pops up that lists which data the user opens to access. The window did not request access to private messages, but in fact the application received it.

On December 6, Twitter reported that it had solved the problem. Judging by the statement of the company on the HackerOne website, no one had time to take advantage of this vulnerability.

This is not the first social network security error related to the API. In September, Twitter discovered a bug in AAAPI (Account Activity API): the system sent a copy of the user's personal message to a random recipient.

Chrome 73 Released

Now the Android version of popular browser has Lite page mode that speeds up website download and reduces traffic consumption
13 March 2019   223

Google has released another update Chrome.

  • The Android application has Lite pages mode for optimizing pages, speeding up their loading and reducing traffic, as well as a new download manager.
  • Settings for account management and synchronization are collected in a separate section - Sync and Google services.
  • Improved video mode “picture in picture”. A floating window can now make web applications (PWA): chat rooms, instant messengers, video conferencing. And added the button "Skip advertising".
  • It is forbidden to load external resources in scripts provided by extensions. Extension developers now need to use background handlers.

The previous version was released in late January.