high
7.5
CWE
20
Advisory Published
Updated

CVE-2016-7476: Input Validation

First published: Thu May 11 2017(Updated: )

The Traffic Management Microkernel (TMM) in F5 BIG-IP LTM, AAM, AFM, APM, ASM, GTM, Link Controller, PEM, PSM, and WebSafe 11.6.0 before 11.6.0 HF6, 11.5.0 before 11.5.3 HF2, and 11.3.0 before 11.4.1 HF10 may suffer from a memory leak while handling certain types of TCP traffic. Remote attackers may cause a denial of service (DoS) by way of a crafted TCP packet.

Credit: f5sirt@f5.com

Affected SoftwareAffected VersionHow to fix
F5 WebSafe=11.6.0
F5 BIG-IP Protocol Security Manager=11.3.0
F5 BIG-IP Protocol Security Manager=11.4.0
F5 BIG-IP Protocol Security Manager=11.4.1
F5 BIG-IP Policy Enforcement Manager=11.3.0
F5 BIG-IP Policy Enforcement Manager=11.4.0
F5 BIG-IP Policy Enforcement Manager=11.4.1
F5 BIG-IP Policy Enforcement Manager=11.5.0
F5 BIG-IP Policy Enforcement Manager=11.5.1
F5 BIG-IP Policy Enforcement Manager=11.5.2
F5 BIG-IP Policy Enforcement Manager=11.5.3
F5 BIG-IP Policy Enforcement Manager=11.6.0
F5 BIG-IP Link Controller=11.3.0
F5 BIG-IP Link Controller=11.4.0
F5 BIG-IP Link Controller=11.4.1
F5 BIG-IP Link Controller=11.5.0
F5 BIG-IP Link Controller=11.5.1
F5 BIG-IP Link Controller=11.5.2
F5 BIG-IP Link Controller=11.5.3
F5 BIG-IP Link Controller=11.6.0
Riverbed SteelApp Traffic Manager=11.3.0
Riverbed SteelApp Traffic Manager=11.4.0
Riverbed SteelApp Traffic Manager=11.4.1
Riverbed SteelApp Traffic Manager=11.5.0
Riverbed SteelApp Traffic Manager=11.5.1
Riverbed SteelApp Traffic Manager=11.5.2
Riverbed SteelApp Traffic Manager=11.5.3
Riverbed SteelApp Traffic Manager=11.6.0
F5 Application Security Manager=11.3.0
F5 Application Security Manager=11.4.0
F5 Application Security Manager=11.4.1
F5 Application Security Manager=11.5.0
F5 Application Security Manager=11.5.1
F5 Application Security Manager=11.5.2
F5 Application Security Manager=11.5.3
F5 Application Security Manager=11.6.0
F5 Access Policy Manager=11.3.0
F5 Access Policy Manager=11.4.0
F5 Access Policy Manager=11.4.1
F5 Access Policy Manager=11.5.0
F5 Access Policy Manager=11.5.1
F5 Access Policy Manager=11.5.2
F5 Access Policy Manager=11.5.3
F5 Access Policy Manager=11.6.0
F5 BIG-IP Advanced Firewall Manager=11.3.0
F5 BIG-IP Advanced Firewall Manager=11.4.0
F5 BIG-IP Advanced Firewall Manager=11.4.1
F5 BIG-IP Advanced Firewall Manager=11.5.0
F5 BIG-IP Advanced Firewall Manager=11.5.1
F5 BIG-IP Advanced Firewall Manager=11.5.2
F5 BIG-IP Advanced Firewall Manager=11.5.3
F5 BIG-IP Advanced Firewall Manager=11.6.0
F5 BIG-IP Application Acceleration Manager=11.3.0
F5 BIG-IP Application Acceleration Manager=11.4.0
F5 BIG-IP Application Acceleration Manager=11.4.1
F5 BIG-IP Application Acceleration Manager=11.5.0
F5 BIG-IP Application Acceleration Manager=11.5.1
F5 BIG-IP Application Acceleration Manager=11.5.2
F5 BIG-IP Application Acceleration Manager=11.5.3
F5 BIG-IP Application Acceleration Manager=11.6.0
Riverbed SteelApp Traffic Manager=11.3.0
Riverbed SteelApp Traffic Manager=11.4.0
Riverbed SteelApp Traffic Manager=11.4.1
Riverbed SteelApp Traffic Manager=11.5.0
Riverbed SteelApp Traffic Manager=11.5.1
Riverbed SteelApp Traffic Manager=11.5.2
Riverbed SteelApp Traffic Manager=11.5.3
Riverbed SteelApp Traffic Manager=11.6.0

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

  • What is the severity of CVE-2016-7476?

    CVE-2016-7476 has been rated as a medium severity vulnerability due to the potential for remote attackers to exploit the memory leak.

  • How do I fix CVE-2016-7476?

    To mitigate CVE-2016-7476, upgrade to the patched versions provided in the F5 security advisory, specifically after the recommended hotfixes.

  • What products are affected by CVE-2016-7476?

    CVE-2016-7476 affects multiple F5 BIG-IP products including LTM, AAM, AFM, APM, ASM, GTM, and others before specific hotfix versions.

  • Can CVE-2016-7476 lead to denial of service?

    Yes, exploitation of CVE-2016-7476 can lead to a denial of service due to resource exhaustion caused by the memory leak.

  • Is there a workaround for CVE-2016-7476?

    While applying the appropriate hotfix is the recommended action, ensuring proper traffic filtering may serve as a temporary workaround for CVE-2016-7476.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203