CVE-2016-9244 in the critical feed json
A BIG-IP virtual server configured with a Client SSL profile that has the non-default Session Tickets option enabled may leak up to 31 byte…
published 2017-02-09 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-10055
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 74.0%
- EPSS 74.0% chance of exploitation in 30 days, percentile 99.4%
- public exploits
- 2
- Exploit-DB
Summary
A BIG-IP virtual server configured with a Client SSL profile that has the non-default Session Tickets option enabled may leak up to 31 bytes of uninitialized memory. A remote attacker may exploit this vulnerability to obtain Secure Sockets Layer (SSL) session IDs from other sessions. It is possible that other data from uninitialized memory may be returned as well.
Timeline
- Published
- First public exploit (EDB-41298)
Exploit prediction
74.00% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
Affected products
- F5 Networks F5 BIG-IP LTM, AAM, AFM, Analytics, APM, ASM, GTM, Link Controller, PEM, PSM
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
exploit-db.com
/exploits/41298/
exploit
-
support.f5.com
/csp/article/K05121675
mitigation, vendor-advisory
- filippo.io /Ticketbleed/
-
securityfocus.com
/bid/96143
vdb-entry
- blog.filippo.io /finding-ticketbleed/
-
securitytracker.com
/id/1037800
vdb-entry, third-party-advisory
- packetstormsecurity.com /files/141017/Ticketbleed-F5-TLS-Information-Disclosure.html
- github.com /0x00string/oldays/blob/master/CVE-2016-9244.py
Sources
- CVE List CVE-2016-9244
- NVD CVE-2016-9244
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.