Skip to content
By using Twitter’s services you agree to our Cookies Use. We and our partners operate globally and use cookies, including for analytics, personalisation, and ads.

This is the legacy version of twitter.com. We will be shutting it down on June 1, 2020. Please switch to a supported browser, or disable the extension which masks your browser. You can see a list of supported browsers in our Help Center.

  • Home Home Home, current page.
  • About

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @
  • Language: English
    • Bahasa Indonesia
    • Bahasa Melayu
    • Català
    • Čeština
    • Dansk
    • Deutsch
    • English UK
    • Español
    • Filipino
    • Français
    • Hrvatski
    • Italiano
    • Magyar
    • Nederlands
    • Norsk
    • Polski
    • Português
    • Română
    • Slovenčina
    • Suomi
    • Svenska
    • Tiếng Việt
    • Türkçe
    • Ελληνικά
    • Български език
    • Русский
    • Српски
    • Українська мова
    • עִבְרִית
    • العربية
    • فارسی
    • मराठी
    • हिन्दी
    • বাংলা
    • ગુજરાતી
    • தமிழ்
    • ಕನ್ನಡ
    • ภาษาไทย
    • 한국어
    • 日本語
    • 简体中文
    • 繁體中文
  • Have an account? Log in
    Have an account?
    · Forgot password?

    New to Twitter?
    Sign up
taviso's profile
Tavis Ormandy
Tavis Ormandy
Tavis Ormandy
Verified account
@taviso

Tweets

Tavis OrmandyVerified account

@taviso

Vulnerability researcher at Google. This is a personal stream, opinions expressed are mine.

California
taviso.decsystem.org
Joined April 2008

Tweets

  • © 2020 Twitter
  • About
  • Help Center
  • Terms
  • Privacy policy
  • Imprint
  • Cookies
  • Ads info
Dismiss
Previous
Next

Go to a person's profile

Saved searches

  • Remove
  • In this conversation
    Verified accountProtected Tweets @
Suggested users
  • Verified accountProtected Tweets @
  • Verified accountProtected Tweets @

Promote this Tweet

Block

  • Tweet with a location

    You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more

    Your lists

    Create a new list


    Under 100 characters, optional

    Privacy

    Copy link to Tweet

    Embed this Tweet

    Embed this Video

    Add this Tweet to your website by copying the code below. Learn more

    Add this video to your website by copying the code below. Learn more

    Hmm, there was a problem reaching the server.

    By embedding Twitter content in your website or app, you are agreeing to the Twitter Developer Agreement and Developer Policy.

    Preview

    Why you're seeing this ad

    Log in to Twitter

    · Forgot password?
    Don't have an account? Sign up »

    Sign up for Twitter

    Not on Twitter? Sign up, tune into the things you care about, and get updates as they happen.

    Sign up
    Have an account? Log in »

    Two-way (sending and receiving) short codes:

    Country Code For customers of
    United States 40404 (any)
    Canada 21212 (any)
    United Kingdom 86444 Vodafone, Orange, 3, O2
    Brazil 40404 Nextel, TIM
    Haiti 40404 Digicel, Voila
    Ireland 51210 Vodafone, O2
    India 53000 Bharti Airtel, Videocon, Reliance
    Indonesia 89887 AXIS, 3, Telkomsel, Indosat, XL Axiata
    Italy 4880804 Wind
    3424486444 Vodafone
    » See SMS short codes for other countries

    Confirmation

     

    Welcome home!

    This timeline is where you’ll spend most of your time, getting instant updates about what matters to you.

    Tweets not working for you?

    Hover over the profile pic and click the Following button to unfollow any account.

    Say a lot with a little

    When you see a Tweet you love, tap the heart — it lets the person who wrote it know you shared the love.

    Spread the word

    The fastest way to share someone else’s Tweet with your followers is with a Retweet. Tap the icon to send it instantly.

    Join the conversation

    Add your thoughts about any Tweet with a Reply. Find a topic you’re passionate about, and jump right in.

    Learn the latest

    Get instant insight into what people are talking about now.

    Get more of what you love

    Follow more accounts to get instant updates about topics you care about.

    Find what's happening

    See the latest conversations about any topic instantly.

    Never miss a Moment

    Catch up instantly on the best stories happening as they unfold.

    1. Tavis Ormandy‏Verified account @taviso 9 Jul 2019
      • Report Tweet
      • Report NetzDG Violation

      Tavis Ormandy Retweeted Andrew Levine

      I agree, this scourge of http rpc endpoints are vendors trying to sidestep the NPAPI deprecation.... it was deprecated for a reason! 😬https://twitter.com/drewml/status/1148704362811801602 …

      Tavis Ormandy added,

      Andrew Levine @drewml
      The @zoom_us vuln sucks, but it's definitely not new. This was/is a common approach used to sidestep the NPAPI deprecation in Chrome. Seems like a @taviso favorite: anti virus - https://bugs.chromium.org/p/project-zero/issues/detail?id=693 … logitech - https://bugs.chromium.org/p/project-zero/issues/detail?id=1663 … utorrent - https://bugs.chromium.org/p/project-zero/issues/detail?id=1524 …
      7 replies 84 retweets 283 likes
      Show this thread
      Tavis Ormandy‏Verified account @taviso 9 Jul 2019
      • Report Tweet
      • Report NetzDG Violation

      If you are shipping a http rpc server on localhost and you're not (at the very least) whitelisting Origin, then you're almost certainly exposing your users to some form of vulnerability.

      2:56 PM - 9 Jul 2019
      • 45 Retweets
      • 166 Likes
      • Patrik Johansson Avimanyu Roy Adli Wahid Fenneladon Privacyasaurus Aurorateratops evan j Fernandet tidsoptimist Brian Christie codepref
      4 replies 45 retweets 166 likes
        1. New conversation
        2. Matthew Hardeman‏ @mdhardeman 9 Jul 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @taviso

          Has anyone produced a best-practices guide for this cursed use case? I'd think you'd also want to ensure a whitelisted value for the "Host" header as well for rebinding attacks, etc.

          2 replies 0 retweets 1 like
        3. Yellow Flag at  🏠‏ @WPalant 9 Jul 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @mdhardeman @taviso

          I did, e.g. in https://palant.de/2019/04/11/bogus-security-mechanisms-encrypting-localhost-traffic/ …. Just don't use web servers for communication between browser extensions and applications - use native messaging API which has built-in security mechanisms.

          0 replies 0 retweets 4 likes
        4. End of conversation
        1. New conversation
        2.  🌦‏ @zemnmez 9 Jul 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @taviso

          https://bugs.chromium.org/p/chromium/issues/detail?id=915538 … >:)

          1 reply 0 retweets 0 likes
        3.  🌦‏ @zemnmez 9 Jul 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @zemnmez @taviso

          i am just posting this so i can act cool when i disclose

          0 replies 0 retweets 4 likes
        4. End of conversation
        1. New conversation
        2. Matthew Hardeman‏ @mdhardeman 9 Jul 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @taviso

          I really really wish the browsers would, upon discovering a resource access of any sort is destined to an on-host IP target, require that the page origin _also be_ an on-host IP. The browser shouldn't be modifying [ or communicating with] desktop software.

          1 reply 0 retweets 1 like
        3. Yellow Flag at  🏠‏ @WPalant 9 Jul 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @mdhardeman @taviso

          There have been quite a few application which relied on websites accessing localhost servers, Google Desktop Search comes to mind in particular (thanks to various vulnerabilities). This should be fine as long as the local server does Origin checks. But too often they don't...

          0 replies 0 retweets 0 likes
        4. End of conversation
        1. New conversation
        2. Yellow Flag at  🏠‏ @WPalant 9 Jul 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @taviso

          I've seen several variations of this myself. Origin whitelisting is hard to get right cross-browser, which is why vendors prefer other solutions. One used a shared secret that they would get via native messaging. And of course they leaked the secret to websites.

          1 reply 0 retweets 1 like
        3. Yellow Flag at  🏠‏ @WPalant 9 Jul 2019
          • Report Tweet
          • Report NetzDG Violation
          Replying to @WPalant @taviso

          Of course they could have avoided the whole issue by just using native messaging for everything. But - hey, IE compatibility is sooooo important...

          0 replies 0 retweets 0 likes
        4. End of conversation

      Loading seems to be taking a while.

      Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.

        Promoted Tweet

        false

        • © 2020 Twitter
        • About
        • Help Center
        • Terms
        • Privacy policy
        • Imprint
        • Cookies
        • Ads info