F5 BIG-IP Flaw Lets Attackers Overflow Memory Through a Single Authorisation Header
Security researchers at watchTowr Labs have published an analysis of a serious flaw in F5's BIG-IP, an application delivery controller that sits in front of business applications and directs traffic to them. F5 published an advisory (K000162605) on 22 September, and the researchers say the vulnerability is already being exploited by attackers.
BIG-IP often sits at the very edge of a network. Depending on licensing, it handles load balancing, TLS offloading, DNS, a web application firewall and remote access and single sign-on. As watchTowr put it, it terminates your TLS, sees traffic in plaintext and holds the keys to your authentication.
To understand the bug, the researchers set up a BIG-IP appliance with a virtual server using an OAuth profile, then compared patched and unpatched versions of the software. The fix was simple: before the patch, the code copied a value into a heap buffer without checking its size, and now it does. The researchers say this is a 20-year-old class of mistake, found in the code that handles security credentials.
They reported that sending an Authorization header larger than 0x4100 bytes to an OAuth endpoint crashed the process by corrupting heap memory. They then described turning the crash into code execution. In about 90% of their runs, a function pointer landed just past the overflowed buffer, which they could overwrite. Protections such as ASLR and a non-executable heap and stack made this harder, and SELinux blocked their first attempts to run commands or write a web shell. They then noticed a hook script that runs whenever the target process crashes, and used it as another route. The excerpt we reviewed ends there, so the full technical details are in the original research.
Why it matters
The vulnerable code sits in the credential handling of a device that sees traffic in plaintext, so a compromise reaches well beyond one appliance. The research also shows that hardening such as ASLR, a non-executable heap and SELinux slowed exploitation but did not stop it, so teams should not treat those controls as a substitute for patching. Because exploitation is reported as already under way, the decision is no longer when to schedule the fix but whether the device has already been touched.
What to do
- Review F5 advisory K000162605 and confirm whether your BIG-IP versions are listed as affected.
- Apply the fixed BIG-IP release from the advisory as a priority.
- Check whether an APM OAuth profile is configured on any virtual server, since this is the exposed feature.
- Look in logs for unusually large Authorization headers sent to OAuth endpoints and for repeated process crashes.