CVE-2016-9247: Input Validation

Published Jan 10, 2017

Updated

Under certain conditions for BIG-IP systems using a virtual server with an associated FastL4 profile and TCP analytics profile, a specific sequence of packets may cause the Traffic Management Microkernel (TMM) to restart.

Affected Software

20 affected components

F5 Big-ip Local Traffic Manager=12.1.0

F5 Big-ip Local Traffic Manager=12.1.1

F5 Big-ip Application Acceleration Manager=12.1.0

F5 Big-ip Application Acceleration Manager=12.1.1

F5 BIG-IP Advanced Firewall Manager=12.1.0

F5 BIG-IP Advanced Firewall Manager=12.1.1

F5 BIG-IP Analytics=12.1.0

F5 BIG-IP Analytics=12.1.1

F5 BIG-IP Access Policy Manager=12.1.0

F5 BIG-IP Access Policy Manager=12.1.1

F5 BIG-IP Application Security Manager=12.1.0

F5 BIG-IP Application Security Manager=12.1.1

F5 Big-ip Domain Name System=12.1.0

F5 Big-ip Domain Name System=12.1.1

F5 Big-ip Link Controller=12.1.0

F5 Big-ip Link Controller=12.1.1

F5 Big-ip Policy Enforcement Manager=12.1.0

F5 Big-ip Policy Enforcement Manager=12.1.1

F5 Big-ip Websafe=12.1.0

F5 Big-ip Websafe=12.1.1

Event History

Jan 10, 2017

CVE Published

via MITRE·04:00 PM

Data Sourced

via MITRE·04:00 PM

DescriptionWeakness

Data Sourced

via NVD·04:59 PM

DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

What is the severity of CVE-2016-9247?

CVE-2016-9247 has been assigned a medium severity rating due to the potential for service interruption.

How do I fix CVE-2016-9247?

To mitigate CVE-2016-9247, upgrade to a patched version of the affected F5 BIG-IP software.

What software is affected by CVE-2016-9247?

CVE-2016-9247 affects specific versions of F5 BIG-IP Local Traffic Manager, Application Acceleration Manager, Advanced Firewall Manager, Analytics, and other associated products.

Can CVE-2016-9247 be exploited remotely?

Yes, CVE-2016-9247 can be exploited by sending a specific sequence of packets to an affected F5 BIG-IP virtual server.

What is the impact of CVE-2016-9247?

The impact of CVE-2016-9247 is that it may cause the Traffic Management Microkernel (TMM) to restart, leading to service disruptions.