Bug ID 561500: ICAP Parsing improvement

Last Modified: Oct 25, 2026

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3, 12.0.0, 12.0.0 hf1, 12.0.0 hf2, 12.0.0 hf3, 12.0.0 hf4

Fixed In:
13.0.0, 12.1.2

Opened: Dec 04, 2015

Severity: 4-Minor

Symptoms

If a malformed ICAP message is sent to the Big-IP the ICAP parser can enter a state where it consumes an increasing amount of CPU and memory.

Impact

Memory and CPU usage increase. Eventually the TMM may crash causing Big-IP fail-over.

Conditions

A request-adapt or response-adapt profile is configured. An ICAP message is received from an ICAP server lacking "ICAP/1.0" as initial header line.

Workaround

None

Fix Information

ICAP parser checks for correct initial ICAP/1.0 header line and rejects message if missing.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips