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
wdormann's profile
Will Dormann
Will Dormann
Will Dormann
@wdormann

Tweets

Will Dormann

@wdormann

Vulnerability Analyst at the CERT/CC. My thoughts are my own, not my employer's.

Joined August 2012

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. Will Dormann‏ @wdormann 5 Feb 2019
      • Report Tweet
      • Report NetzDG Violation

      Despite Exchange 2010 not being affected by the #privexchange PoC in my testing, Microsoft has listed Exchange 2010 in their new advisory: https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV190007 … Perhaps they know of a variant that affects 2010. Still no update at this time, so be sure to apply workarounds!

      2 replies 3 retweets 5 likes
      Show this thread
    2. Will Dormann‏ @wdormann 5 Feb 2019
      • Report Tweet
      • Report NetzDG Violation

      But then again, this advisory states "To exploit the vulnerability, an attacker would need to execute a man-in-the-middle attack", which we know isn't true. So maybe I'll let the dust settle a bit...

      1 reply 0 retweets 2 likes
      Show this thread
    3. Will Dormann‏ @wdormann 5 Feb 2019
      • Report Tweet
      • Report NetzDG Violation

      It also states "An attacker who successfully exploited this vulnerability could attempt to impersonate any other user of the Exchange server." This is worded in a way that implies that perhaps the impact is that User A can read the email of User B. It can get you DOMAIN ADMIN!

      2 replies 1 retweet 2 likes
      Show this thread
    4. Will Dormann‏ @wdormann 6 Feb 2019
      • Report Tweet
      • Report NetzDG Violation

      And you might ask yourself: How did @msftsecresponse advisory https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV190007 … get published without mentioning CVE-2019-0686? Story time: At some point, MSRC stopped using bulletin identifiers like MS08-067, and started using CVE IDs instead. This is a good thing, right?

      1 reply 1 retweet 1 like
      Show this thread
      Will Dormann‏ @wdormann 6 Feb 2019
      • Report Tweet
      • Report NetzDG Violation

      Not so fast... When this change happened, MSRC adopted the incorrect mindset that a CVE ID is used to refer to a software update, rather than a vulnerability. Because no software update has been released for Exchange, Microsoft has not yet publicly referred to it by its CVE ID.

      3:29 PM - 6 Feb 2019
      • 6 Likes
      • Art Manion Trent Novelly Eli Grey Vadim Sterkin Sciuridae Hero
      0 replies 0 retweets 6 likes

      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