lolloj - Fotolia
An F5 Networks bug, known as Ticketbleed, was recently discovered. Ticketbleed apparently caused uninitialized memory, including session IDs, to leak from certain F5 products. What are session IDs, and how can attackers use them?
A session ID is a piece of data that keeps track of what a user does when he visits a website for a certain duration of time or for a session. It can be stored as a cookie, form field or URL.
With Ticketbleed, up to 31 bytes of uninitialized memory may leak from, for example, an F5 virtual server configured with a client SSL profile that has the session ticket enabled to speed up resumed and repeated connections.
Before the leakage can occur, the user supplies a session ID together with the ticket to the server. The server, in turn, echoes back that the ticket has been accepted.
At the same time, the F5 stack echoes back 32 bytes of memory, even if the session ID was shorter. This means the attackers can provide a one byte session ID, and then get back 31 bytes of uninitialized memory.
The attackers taking advantage of Ticketbleed can obtain session IDs from other sessions. It is possible for them to get other data from uninitialized memory and cookies.
Disabling cookies is not always practical. A better option is to take the following five steps to disable the session ticket feature, protecting your systems from Ticketbleed:
- Log in to the configuration utility.
- Navigate to the client via local traffic, then to profiles and SSL.
- Toggle the option for configuration from basic to advanced.
- Uncheck session ticket to disable the feature.
- Click update to save the changes.
However, the downside of this fix is that disabling session tickets may cause the connection performance to degrade. Enterprises should keep this in mind when considering their options for addressing session ID security issues like Ticketbleed.
Ask the expert:
Want to ask Judith Myerson a question about security? Submit your question now via email. (All questions are anonymous.)
Learn about Bloom filters on cookies and what they mean for privacy
Find out why session cookies should be protected by a salted hash
Discover the effect the Yahoo breach has had on authentication cookies
Dig Deeper on Endpoint protection and client security
Related Q&A from Judith Myerson
The Constrained Application Protocol underpins IoT networks. But the protocol could allow a threat actor to launch an attack. Continue Reading
Dutch researchers discovered flaws in ATA security and TCG Opal affecting self-encrypting drives. What steps can you take to guard data stored on ... Continue Reading
The Signal Desktop application was found to be making decryption keys available in plaintext. Learn how the SQLite database and plaintext passwords ... Continue Reading