How to fix: F5 BIG-IP Cookie May Expose Internal IP
An F5 BIG-IP persistence cookie (BIGipServer*) was observed. Depending on the load balancer's configuration, its value can encode the internal pool member's IP address and port.
Why it matters
An attacker who decodes the cookie value learns internal network topology (private IP ranges, port numbers) that would otherwise not be reachable from outside the network, aiding further attacks.
By default, F5 BIG-IP's cookie-based persistence encodes the selected pool member's IP and port directly in the cookie value using a simple, publicly documented, reversible encoding. F5 supports an 'insert' mode with encryption to prevent this, but it is not the default in every configuration.
How to fix it
- 1Enable cookie encryption for BIG-IP persistence cookies (LTM Cookie Encryption).
- 2Alternatively, switch to an opaque session-based persistence method that does not embed pool member details in the cookie.
- 3Ensure internal pool member IPs are not otherwise reachable even if disclosed.
Code examples
Enable BIG-IP cookie encryption (tmsh)
tmsh modify ltm profile cookie-persistence my_cookie_persist cookie-encryption required cookie-encryption-passphrase <passphrase>References
Detected automatically by VulnRadar. The check id is f5-bigip-cookie-exposes-internal-ip, stable across every scan so you can filter or diff on it.
More cookies checks
- LowCookie Domain Attribute Is Too Broad
- LowCookie Missing Secure Attribute
- InfoThird-Party Cookie Missing Partitioned Attribute
- High__Host- Prefix Cookie Missing Secure Attribute
- High__Host- Prefix Cookie with Non-Root Path
- High__Secure- Prefix Cookie Missing Secure Attribute
- LowCookie Expires/Max-Age Exceeds 1 Year
- InfoCookie Name Leaks Framework or Language
Questions
- How severe is F5 BIG-IP Cookie May Expose Internal IP?
- VulnRadar rates this medium severity in the cookies category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id f5-bigip-cookie-exposes-internal-ip, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does F5 BIG-IP Cookie May Expose Internal IP map to?
- It maps to CWE-200. In the OWASP Top 10 it falls under A05:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.