Bug ID 497395: Correctly assign severity to check component alerts

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP FPS(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

Fixed In:
12.0.0, 11.6.1

Opened: Dec 18, 2014
Severity: 3-Major

Symptoms

Check component alerts can be caused by legitimate browser settings. There is no way to distinguish this from malware alerts.

Impact

Difficult to identify users that are infected with malware.

Conditions

Check component alerts are sent.

Workaround

None

Fix Information

Differentiate between low severity and high severity component check alerts.

Behavior Change

A new DB variable "AntiFraud.ComponentsValidation.Method" has been added that controls the type of request that the component check is performed on (all, get, post, or none)