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
colmmacc's profile
Colm MacCárthaigh
Colm MacCárthaigh
Colm MacCárthaigh
@colmmacc

Tweets

Colm MacCárthaigh

@colmmacc

AWS, Apache, Crypto, Irish Music, Haiku, Photography

Seattle
notesfromthesound.com
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. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
      • Report Tweet
      • Report NetzDG Violation

      Colm MacCárthaigh Retweeted Robert Merget

      Congratulations and thanks to @jurajsomorovsky, @NimrodAviram and @ic0nz1 who reported this to AWS in November last year. This was a really interesting find that took a lot of diving! Story ...https://twitter.com/ic0nz1/status/1100413895141773312 …

      Colm MacCárthaigh added,

      Robert Merget @ic0nz1
      For our Usenix Paper we found a lot of Padding Oracle Vulnerabilities in TLS stacks of the Alexa Top-1 Million, including Citrix and OpenSSL. With @jurajsomorovsky @NimrodAviram @craigtweets @JanisFliegens and others. Check our current findings at: https://github.com/RUB-NDS/TLS-Padding-Oracles …
      1 reply 28 retweets 57 likes
      Show this thread
    2. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
      • Report Tweet
      • Report NetzDG Violation

      Reassuring standard practice tweet: if you're using AWS services or AWS to terminate TLS/SSL you don't need to do anything. Amazon s2n, our Open Source implementation of TLS, was not impacted (more about why later).

      1 reply 0 retweets 4 likes
      Show this thread
    3. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
      • Report Tweet
      • Report NetzDG Violation

      If you're using OpenSSL OpenSSL 1.0.x on your own instances, you're probably still not impacted, and if you are the risk is low, but go ahead and upgrade to OpenSSL 1.0.2r anyway! It was released this morning. O.k. story ...

      2 replies 3 retweets 4 likes
      Show this thread
    4. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
      • Report Tweet
      • Report NetzDG Violation

      Juraj, Robert, Nimrod built a scanning tool that scans the internet for padding oracles. TLS supports a number of ciphers suites, and the older CBC ones encrypt in fixed size blocks. If the data you're sending doesn't add up to a whole block size, some padding is added.

      1 reply 2 retweets 6 likes
      Show this thread
    5. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
      • Report Tweet
      • Report NetzDG Violation

      When a CBC record comes in, it can be malformed in 2 ways: the padding can be wrong, or the signature (aka the MAC) can be wrong. Because the TLS design got the order of padding and MACs the wrong way around, it's important that implementations don't reveal which is wrong.

      1 reply 1 retweet 3 likes
      Show this thread
    6. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
      • Report Tweet
      • Report NetzDG Violation

      If implementations do, this is called a padding oracle attack, and if an attacker can get an implementation to encrypt the same data repeatedly, and also modify the encrypted traffic, and also observe the difference, eventually they would be able to decrypt the data. Sounds bad!

      1 reply 1 retweet 7 likes
      Show this thread
    7. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
      • Report Tweet
      • Report NetzDG Violation

      So the scanning tool does something simple: it negotiates a CBC cipher suite, and makes a connection with a bad MAC and a connection with bad padding and looks for any difference. This is my favorite kind of science: actually go check the real world!

      1 reply 0 retweets 2 likes
      Show this thread
    8. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
      • Report Tweet
      • Report NetzDG Violation

      Not to brag, but AWS is popular. Scan us and you'll find literally millions of IPs that are terminating TLS/SSL, mostly on behalf of customers for their web applications, web services, and websites. Out of these, the scanning tool found at least 100s that showed differences.

      1 reply 0 retweets 2 likes
      Show this thread
    9. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
      • Report Tweet
      • Report NetzDG Violation

      In the report we got, it was a "strange" list: customer IPs running unknown software, load balancers that were in FIPS mode, load balancers running on old hardware, there didn't seem to be much in common.

      1 reply 0 retweets 4 likes
      Show this thread
    10. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
      • Report Tweet
      • Report NetzDG Violation

      We also have our own tests and monitoring for padding oracles. You can see s2n's here: https://github.com/awslabs/s2n/blob/master/tests/unit/s2n_cbc_verify_test.c … , and re-running these checks would actually show no impact. Head-scratcher!

      1 reply 0 retweets 2 likes
      Show this thread
      Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
      • Report Tweet
      • Report NetzDG Violation

      Colm MacCárthaigh Retweeted juraj somorovsky

      At this point Steven Collison and Andrew Hourselt from our TLS/SSL team started having to dive really deep to find out what was going on.https://twitter.com/jurajsomorovsky/status/1100420753256841218 …

      Colm MacCárthaigh added,

      juraj somorovsky @jurajsomorovsky
      Reporting the OpenSSL bug would not be possible without @colmmacc and his colleagues. We just reported an invalid behavior, they performed all the hard analyses (https://twitter.com/ic0nz1/status/1100413895141773312 …). Unfortunately, not all security teams are so collaborative
      8:10 AM - 26 Feb 2019
      • 5 Likes
      • Jon Zobrist cliche guevara Alex Weibel Mahesh V juraj somorovsky
      1 reply 0 retweets 5 likes
        1. New conversation
        2. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
          • Report Tweet
          • Report NetzDG Violation

          First we were able to determine that most of the IPs were using OpenSSL to terminate traffic. But it wasn't always impacted. In fact the really common OpenSSL users, software like nginx, Apache ... not impacted at all!

          1 reply 1 retweet 1 like
          Show this thread
        3. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
          • Report Tweet
          • Report NetzDG Violation

          Tracing through the code of things that were impacted showed that the problem only happened when the application called SSL_shutdown() twice, even if there is a protocol error.

          1 reply 0 retweets 2 likes
          Show this thread
        4. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
          • Report Tweet
          • Report NetzDG Violation

          Calling SSL_shutdown() twice is normal when there's no problem with a connection, and it should be harmless in the error case, so it's understandable that some applications do it ... but thankfully it's not common.

          1 reply 0 retweets 1 like
          Show this thread
        5. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
          • Report Tweet
          • Report NetzDG Violation

          The actual leak of info, whether it was a padding or MAC error, would effectively show up as a timing or connection close difference between these calls. Impacted applications would either seem to time out, or close connections, differently, depending on the error. Subtle.

          1 reply 0 retweets 4 likes
          Show this thread
        6. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
          • Report Tweet
          • Report NetzDG Violation

          O.k. so next question: why don't existing padding oracle tests find this? Well it turns out only to happen to zero byte records. Records that have no data in them. And the scanning tool happens to send zero byte records.

          1 reply 0 retweets 2 likes
          Show this thread
        7. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
          • Report Tweet
          • Report NetzDG Violation

          Zero-byte records aren't common: browsers don't send them afaict, and packet dumps seem to show that they are exceedingly rare: which makes sense, if you have no data to send, why would bother? So that's very re-assuring.

          1 reply 1 retweet 2 likes
          Show this thread
        8. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
          • Report Tweet
          • Report NetzDG Violation

          Next weird thing: the problem also happened if OpenSSL wasn't using AES-NI hardware acceleration. In practice this means it impacted 3DES (which people should have turned off for other reasons!) and older hardware.

          1 reply 1 retweet 3 likes
          Show this thread
        9. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
          • Report Tweet
          • Report NetzDG Violation

          This also explained why FIPS software appeared in the list, because FIPS software generally can't use AES-NI.

          1 reply 0 retweets 2 likes
          Show this thread
        10. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
          • Report Tweet
          • Report NetzDG Violation

          At this point, a lot of factors have to be combined: TLS sw would have to be coded in an uncommon way, using OpenSSL, negotiating older cipher suites, on older HW, with clients that send 0-byte records, and can be made repeat the same data over and over, with an active MITM.

          2 replies 1 retweet 2 likes
          Show this thread
        11. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
          • Report Tweet
          • Report NetzDG Violation

          But that makes it more interesting! How do we find and prevent even these kind of rarefied cases? Automation, like the scanning tool, is clearly critical - but can we do more at the point of code?

          1 reply 0 retweets 3 likes
          Show this thread
        12. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
          • Report Tweet
          • Report NetzDG Violation

          One thing I'm grateful for is that in s2n we kill connections on any error, and we do it in a way where s2n will completely refuse to interact with the connection after the error has happened. Just with a closed flag ... https://github.com/awslabs/s2n/blob/master/tls/s2n_connection.c#L1031 …

          2 replies 1 retweet 1 like
          Show this thread
        13. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
          • Report Tweet
          • Report NetzDG Violation

          s2n uses OpenSSL's libcrypto for the underlying cryptography, and the same issue in that code /could/ have caused impact within s2n were it not for that practice. Basically this check .... https://github.com/awslabs/s2n/blob/master/tls/s2n_send.c#L94 …

          1 reply 0 retweets 1 like
          Show this thread
        14. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
          • Report Tweet
          • Report NetzDG Violation

          Of course the impact still would have been small, because of the other factors, but I'm glad we have that check! Anyway, thanks again to the issue reporters, read their paper when it comes! and thanks for Andrew and Steven from the TLS team. That's it, unless AMA.

          1 reply 0 retweets 5 likes
          Show this thread
        15. Colm MacCárthaigh‏ @colmmacc 26 Feb 2019
          • Report Tweet
          • Report NetzDG Violation

          Colm MacCárthaigh Retweeted Robert Merget

          Quick addendum:https://twitter.com/ic0nz1/status/1100432621149003783 …

          Colm MacCárthaigh added,

          Robert Merget @ic0nz1
          Replying to @colmmacc
          actually you do not need clients which send 0-byte records. An Attacker can cut the record (adjust the iv) and adjust the length of the record header. This way a normal record appears to the server as zero length with an invalid mac, although the original record was way longer
          2 replies 1 retweet 3 likes
          Show this thread
        16. 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