SOL05272632 - BIG-IP AOM password sync vulnerability CVE-2015-8611

Vulnerability Recommended Actions

If you are running a version listed in the Versions known to be vulnerablecolumn, you can eliminate this vulnerability by upgrading to a version listed in the Versions known to be not vulnerablecolumn. If the table lists only an older version than what you are currently running, or does not list a non-vulnerable version, then no upgrade candidate currently exists.

F5 responds to vulnerabilities in accordance with the Severity values published in the previous table. TheSeverity values and other security vulnerability parameters are defined in SOL4602: Overview of the F5 security vulnerability response policy.

To mitigate this vulnerability, you can perform one or both of the following procedures:

Manually synchronizing the AOM password

Impact of action: The following mitigation suggestions should not have a negative impact on your system, but may require additional administration steps in the event of a Traffic Management Operating System (TMOS) password change.

If you have deployed a new BIG-IP 12.0.0 system on an affected platform, changing the root password in TMOS fails to synchronize with AOM and leaves the default password. To change passwords, you can first change the password in TMOS, and then synchronize the TMOS and AOM passwords by logging in to the advanced shell(bash) as the root user and running the**/usr/bin/syncpwd **command.

If you have upgraded to BIG-IP 12.0.0 from an existing TMOS installation, the root password that was set in the previous installation will persist in AOM. Upon upgrading to BIG-IP 12.0.0, password synchronization fails and AOM still uses the password synchronized from the previous system installation. To change passwords, you can first change the password in TMOS, and then synchronize the TMOS and AOM passwords by logging in to bash as the root user and running the**/usr/bin/syncpwd** command.

Note: Any subsequent change to the root password must be manually synchronized to AOM using the previous instructions.

Disabling network access to AOM

Impact of action: The following mitigation suggestion should not have a negative impact on your system, but you will be unable to access AOM via the network.

For instructions and more information about disabling network access to AOM, refer to SOL14595: Configuring AOM network access (2000, 4000, 5000, 7000, and 10000 series platforms).

Supplemental Information

• SOL9970: Subscribing to email notifications regarding F5 products
• SOL9957: Creating a custom RSS feed to view new and updated documents
• SOL4918: Overview of the F5 critical issue hotfix policy
• SOL167: Downloading software and firmware from F5
• SOL13123: Managing BIG-IP product hotfixes (11.x - 12.x)