CVE intelligence and bounded remediation

CVE-2017-6160 — F5 Big-Ip Application Acceleration Manager security vulnerability

Medium CVSS 5.9

In F5 BIG-IP AAM and PEM software version 12.0.0 to 12.1.1, 11.6.0 to 11.6.1, 11.4.1 to 11.5.4, a remote attacker may create maliciously crafted HTTP request to cause Traffic Management Microkernel (TMM) to restart and temporarily fail to process traffic. This issue is exposed on virtual servers using a Policy Enforcement profile or a Web Acceleration profile. Systems that do not have BIG-IP AAM module provisioned are not vulnerable. The Traffic Management Microkernel (TMM) may restart and temporarily fail to process traffic. Systems that do not have BIG-IP AAM or PEM module provisioned are not vulnerable.

Severity
Medium
CVSS
5.9 (3.0)
Published
2017-10-27
CISA KEV
Not currently listed
Ecosystem
software/application

Affected products

  • 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

Showing 6 representative product identities from 26 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

General vulnerability remediation

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Confirm the affected component, deployment paths, reachable interfaces, and enabled features from inventories and configuration, without probing production destructively.
  • Compare the advisory's affected conditions with the repository lockfiles, build manifests, artifacts, and runtime inventory.
  • Identify data sensitivity, trust boundaries, and privilege level for every confirmed affected deployment.

Remediate safely

  • Apply a vendor-supported fix or remove the affected component or feature; record the selected change and its source in the repository.
  • Update direct and transitive dependency locks, generated artifacts, deployment manifests, and asset inventories together.
  • Add a regression test for the documented unsafe condition using inert inputs and preserve rollback instructions.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.