HighPublic exploit

Ticketbleed in F5 BIG-IP Client SSL Session Tickets

IdentifiersCVE-2016-9244CWE-200· Exposure of Sensitive Information…Also known asticketbleed

CVE-2016-9244, commonly referred to as Ticketbleed, affects F5 BIG-IP virtual servers configured with a Client SSL profile where the non-default Session Tickets option is enabled. In this condition, the device may return up to 31 bytes of uninitialized memory in TLS session ticket-related processing. According to the provided content, a remote attacker can exploit the issue to obtain SSL session IDs from other sessions, and other residual data from uninitialized memory may also be exposed. The vulnerability is an information disclosure issue caused by exposure of uninitialized memory during SSL/TLS handling.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote unauthenticated attacker to read small portions of process memory, up to 31 bytes per affected response. The disclosed data can include SSL session IDs belonging to other connections and potentially other sensitive residual memory contents. The primary impact is confidentiality loss affecting TLS session material and adjacent memory data; the provided content does not indicate direct code execution, integrity impact, or denial of service as the core consequence.

Mitigation

If you can’t patch tonight, do this now.

As an interim mitigation, disable the non-default Session Tickets option on affected BIG-IP Client SSL profiles where operationally feasible. Limiting exposure of vulnerable virtual servers from untrusted networks can reduce attack surface, but the content specifically identifies Session Tickets being enabled as the key exploitable condition. Validate mitigation by testing affected endpoints for Ticketbleed exposure after configuration changes.

Remediation

Patch, then assume compromise.

Apply the vendor-provided F5 BIG-IP updates that address CVE-2016-9244. If patch guidance is being followed operationally, prioritize systems exposing affected BIG-IP virtual servers with Client SSL profiles using Session Tickets. Because the issue is tied to the vulnerable TLS implementation behavior, remediation requires upgrading to a fixed BIG-IP version rather than relying solely on client-side changes.

PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).

VALID 1 / 3 TOTALView more in app

TicketbleedMaturityPoCVerified exploit

This repository contains a Go-based proof-of-concept exploit for the Ticketbleed vulnerability (CVE-2016-9244) affecting F5 BIG-IP products. The main exploit logic is in 'Ticketbleed.go.tmp', which, after renaming to 'Ticketbleed.go', can be built and run as a command-line tool. The tool targets a user-supplied IP and port, checks if the server is vulnerable, and if so, exploits the TLS session ticket handling flaw to leak up to 31 bytes of uninitialized memory per request. The repository includes a modified version of Go's crypto/tls library (in the 'src' folder) to facilitate the exploit, as well as extensive test data and supporting code for TLS protocol handling. The exploit is operational and can be used to extract potentially sensitive information from vulnerable F5 BIG-IP systems over the network. No hardcoded endpoints are present; the target is specified at runtime. The codebase is well-structured, with clear separation between the exploit logic, TLS protocol implementation, and test data.

EgeBalciDisclosed Feb 10, 2017gonetwork

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

F5Big-Ip Access Policy Managerapplication

F5Big-Ip Advanced Firewall Managerapplication

F5Big-Ip Analyticsapplication

F5Big-Ip Application Acceleration Managerapplication

F5Big-Ip Application Security Managerapplication

F5Big-Ip Global Traffic Managerapplication

F5Big-Ip Link Controllerapplication

F5Big-Ip Local Traffic Managerapplication

F5Big-Ip Policy Enforcement Managerapplication

F5Big-Ip Protocol Security Moduleapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

2 SOURCESView more in app

rabbitmqNews

Jul 13, 2020

TLS Support | RabbitMQ

A TLS session ticket information disclosure vulnerability referenced in test output showing the evaluated setup is not vulnerable.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity1