# CVE-2016-9244: Information disclosure in F5 BIG-IP LTM, AAM, AFM, Analytics, APM, ASM, GTM, Link Controller, PEM, PSM

> Remote attackers can leak SSL session IDs and uninitialized memory from F5 BIG-IP devices when Session Tickets are enabled.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5855-8rvh-x38f

## What is CVE-2016-9244?

CVE-2016-9244 is a high-severity vulnerability in F5 Big-Ip Access Policy Manager, published on 9 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2016-9244?

It affects 10 products.


Products: F5 Big-Ip Access Policy Manager, F5 Big-Ip Advanced Firewall Manager, F5 Big-Ip Analytics, F5 Big-Ip Application Acceleration Manager, F5 Big-Ip Application Security Manager, F5 Big-Ip Global Traffic Manager, F5 Big-Ip Link Controller, F5 Big-Ip Local Traffic Manager, F5 Big-Ip Policy Enforcement Manager, F5 Big-Ip Protocol Security Module.

## How do I fix CVE-2016-9244?

No fix has been published for CVE-2016-9244 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-9244 being exploited?

There is no known exploitation of CVE-2016-9244 in the wild and no public exploit code.

Public exploit code:

- This is a tool for exploiting Ticketbleed (CVE-2016-9244) vulnerability. (github_poc): https://github.com/EgeBalci/Ticketbleed
- F5 BIG-IP SSL Virtual Server - 'Ticketbleed' Memory Disclosure (exploitdb)
- Minion plugin for checking Ticketbleed (CVE-2016-9244) (github_poc): https://github.com/glestel/minion-ticket-bleed-plugin
- F5 BIG-IP 11.6 SSL Virtual Server - 'Ticketbleed' Memory Disclosure (exploitdb)

## Other vulnerabilities in F5 Big-Ip Access Policy Manager

- [CVE-2023-46747](https://insights.sbomify.com/CVE-2023-46747/): F5 BIG-IP Configuration Utility Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2022-1388](https://insights.sbomify.com/CVE-2022-1388/): F5 BIG-IP Missing Authentication (critical 9.8, exploited in the wild)
- [CVE-2021-22986](https://insights.sbomify.com/CVE-2021-22986/): F5 BIG-IP and BIG-IQ Centralized Management iControl REST Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2021-22991](https://insights.sbomify.com/CVE-2021-22991/): F5 BIG-IP Traffic Management Microkernel Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2020-5902](https://insights.sbomify.com/CVE-2020-5902/): F5 BIG-IP Traffic Management User Interface (TMUI) Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-9244 and fix it if it is affected.

What it is: CVE-2016-9244 is a high-severity vulnerability in F5 Big-Ip Access Policy Manager, published on 9 Feb 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-9244 in the wild and no public exploit code.

Affected product: F5 Big-Ip Access Policy Manager. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-9244/ (Markdown: https://insights.sbomify.com/CVE-2016-9244/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-9244
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-9244
- OSV: https://osv.dev/vulnerability/CVE-2016-9244

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-9244/
Summaries are generated and may contain mistakes; the official description above is the record.