Last Modified: Sep 14, 2023
Affected Product(s):
BIG-IP (all modules)
Known Affected Versions:
11.5.6, 11.5.7, 11.5.8, 11.5.9, 11.5.10, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 12.1.5, 12.1.5.1, 12.1.5.2, 12.1.5.3, 12.1.6, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3, 14.1.5.4, 14.1.5.6, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4
Opened: May 04, 2018 Severity: 4-Minor
The engineID is supposed to be unique per device; however, it is possible to configure the engineID directly and it will synchronize across the device trust to multiple devices.
The engine ID of a device is not unique.
The user has configured a numeric engineID through use of the tmsh sys include directive.
Do not hard code a numeric engine ID. If you do not want to use the generated engine ID then, configure engine ID type and a unique ID will be generated even when the configuration is synchronized.
None