In BIG-IP 14.0.0-188.8.131.52, 184.108.40.206-220.127.116.11, or 18.104.22.168-22.214.171.124, if an MPTCP connection receives a HUDCTL_ABORT while the initial flow is not the primary flow, the initial flow will remain after the MP_FASTCLOSE procedure is complete. TMM may restart and produce a core file as a result of this condition.
In BIG-IP 14.0.0-126.96.36.199 or 13.0.0-188.8.131.52 or Enterprise Manager 3.1.1, when authenticated administrative users run commands in the Traffic Management User Interface (TMUI), also referred to as the BIG-IP Configuration utility, restrictions on allowed commands may not be enforced.
In BIG-IP 14.0.0-184.108.40.206 or 13.0.0-220.127.116.11, iControl and TMSH usage by authenticated users may leak a small amount of memory when executing commands
On BIG-IP APM 14.0.0-18.104.22.168 or 13.0.0-22.214.171.124, TMM may restart when processing a specially crafted request with APM portal access.
On BIG-IP 14.0.0-126.96.36.199, 13.0.0-188.8.131.52, 12.1.0-184.108.40.206, 11.6.0-220.127.116.11, or 11.2.1-11.5.6, BIG-IQ Centralized Management 6.0.0-6.0.1, 5.0.0-5.4.0 or 4.6.0, BIG-IQ Cloud and Orchestration 1.0.0, iWorkflow 2.0.1-2.3.0, or Enterprise Manager 3.1.1 a BIG-IP user granted with tmsh access may cause the BIG-IP system to experience denial-of-service (DoS) when the BIG-IP user uses the tmsh utility to run the edit cli preference command and proceeds to save the changes to another filename repeatedly. This action utilises storage space on the /var partition and when performed repeatedly causes the /var partition to be full.
On BIG-IP 14.0.0-18.104.22.168 or 13.0.0-22.214.171.124, in certain circumstances, when processing traffic through a Virtual Server with an associated MQTT profile, the TMM process may produce a core file and take the configured HA action.
On BIG-IP 14.0.0-126.96.36.199 or 13.0.0-188.8.131.52, undisclosed traffic patterns may lead to denial of service conditions for the BIG-IP system. The configuration which exposes this condition is the BIG-IP self IP address which is part of a VLAN group and has the Port Lockdown setting configured with anything other than "allow-all".
When BIG-IP 14.0.0-184.108.40.206, 13.0.0-220.127.116.11, 12.1.0-18.104.22.168, 11.6.0-22.214.171.124, or 11.2.1-11.5.6, BIG-IQ Centralized Management 5.0.0-5.4.0 or 4.6.0, BIG-IQ Cloud and Orchestration 1.0.0, iWorkflow 2.1.0-2.3.0, or Enterprise Manager 3.1.1 is licensed for Appliance Mode, Admin and Resource administrator roles can by-pass BIG-IP Appliance Mode restrictions to overwrite critical system files. Attackers of high privilege level are able to overwrite critical system files which bypasses security controls in place to limit TMSH commands. This is possible with an administrator or resource administrator roles when granted TMSH. Resource administrator roles must have TMSH access in order to perform this attack.
In BIG-IP 14.0.0-126.96.36.199, 13.0.0-188.8.131.52, 12.1.0-184.108.40.206, 11.6.0-220.127.116.11, or 11.2.1-11.5.6, an attacker sending specially crafted SSL records to a SSL Virtual Server will cause corruption in the SSL data structures leading to intermittent decrypt BAD_RECORD_MAC errors. Clients will be unable to access the application load balanced by a virtual server with an SSL profile until tmm is restarted.
In some situations on BIG-IP APM 14.0.0-18.104.22.168, 13.0.0-22.214.171.124, 12.1.0-126.96.36.199, or 11.6.0-188.8.131.52, the CRLDP Auth access policy agent may treat revoked certificates as valid when the BIG-IP APM system fails to download a new Certificate Revocation List.