Cisco Adaptive Security Appliance Software Privilege Escalation Vulnerability
A vulnerability in the authorization subsystem of Cisco Adaptive Security Appliance (ASA) Software could allow an authenticated, but unprivileged (levels 0 and 1), remote attacker to perform privileged actions by using the web management interface. The vulnerability is due to improper validation of user privileges when using the web management interface. An attacker could exploit this vulnerability by sending specific HTTP requests via HTTPS to an affected device as an unprivileged user. An exploit could allow the attacker to retrieve files (including the running configuration) from the device or to upload and replace software images on the device. Cisco has released software updates that address this vulnerability. There are workarounds that address this vulnerability.
beschreibt (1)
Zugehörige CVEs.
| ID | Schweregrad | ausnutzbar | ||
|---|---|---|---|---|
| CVE-2018-15465US | high8.1OT erhöht | — | ||
A vulnerability in the authorization subsystem of Cisco Adaptive Security Appliance (ASA) Software could allow an authenticated, but unprivileged (levels 0 and 1), remote attacker… | ||||
Referenzen
Externe Belege — Patches, Meldungen, Analysen.
- Cisco Adaptive Security Appliance Software Privilege Escalation Vulnerabilityself
- Cisco Security Vulnerability Policyexternal
- Software Centerexternal
- https://www.cisco.com/c/en/us/products/end-user-license-agreement.htmlexternal
- https://www.cisco.com/c/en/us/support/web/tsd-cisco-worldwide-contacts.htmlexternal
- Cisco ASA Series General Operations ASDM Configuration Guideexternal
- Cisco ASA Configuration Guideexternal
- Cisco ASA Series General Operations CLI Configuration Guideexternal
Behebungen (932)
- Behoben7.0.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.1.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.4.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.5.12
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.6.18
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.6.22
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.6.26
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.6.29
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.6.32
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.6.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.6.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.7
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.7.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.7.12
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.7.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.7.9
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.8.12
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.8.13
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.8.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.0.8.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.1.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.1.2.16
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.1.2.20
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.1.2.24
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.1.2.28
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.1.2.38
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.1.2.42
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.1.2.46
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.1.2.49
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.1.2.53
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.1.2.61
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.1.2.64
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.1.2.72
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.1.2.81
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.1.13
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.1.19
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.1.24
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.1.9
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.2.10
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.2.14
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.2.18
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.2.19
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.2.22
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.2.34
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.2.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.3.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.3.12
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.3.16
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.4.18
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.4.25
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.4.27
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.4.30
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.4.33
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.4.42
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.4.46
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.4.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.4.9
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.5.10
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.5.12
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.5.16
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.5.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.5.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.5.7
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben7.2.5.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.1.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.2.11
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.2.15
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.3.12
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.3.19
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.3.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.4.16
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.4.23
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.4.25
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.4.28
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.4.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.4.31
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.4.32
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.4.33
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.4.38
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.4.39
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.4.44
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.4.9
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.5.20
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.5.23
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.5.25
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.5.27
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.5.28
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.0.5.31
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.1.0.104
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.1.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.1.1.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.1.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.1.2.13
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.1.2.15
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.1.2.16
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.1.2.19
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.1.2.23
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.1.2.24
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.1.2.49
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.1.2.50
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.1.2.55
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.1.2.56
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.0.45
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.1.11
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.2.10
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.2.12
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.2.16
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.2.17
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.2.9
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.4.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.4.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.5.13
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.5.22
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.5.26
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.5.33
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.5.40
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.5.41
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.5.46
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.5.48
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.5.49
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.5.50
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.5.51
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.5.52
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.5.55
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.5.57
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.5.58
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.2.5.59
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.3.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.3.1.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.3.1.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.3.1.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.3.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.3.2.13
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.3.2.23
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.3.2.25
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.3.2.31
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.3.2.33
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.3.2.34
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.3.2.37
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.3.2.39
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.3.2.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.3.2.40
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.3.2.41
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.3.2.44
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.1.11
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.1.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.2.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.2.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.3.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.3.9
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.4.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.4.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.4.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.4.9
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.5.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.6.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.7
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.7.15
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.7.22
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.7.23
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.7.26
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.7.28
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.7.29
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.7.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.7.30
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.4.7.31
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.5.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.5.1.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.5.1.14
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.5.1.17
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.5.1.18
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.5.1.19
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.5.1.21
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.5.1.24
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.5.1.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.5.1.7
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.6.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.6.1.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.6.1.10
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.6.1.12
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.6.1.13
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.6.1.14
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.6.1.15
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.6.1.17
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.6.1.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.6.1.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.7.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.7.1.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.7.1.11
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.7.1.13
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.7.1.16
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.7.1.17
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.7.1.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.7.1.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.7.1.7
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben8.7.1.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.2.10
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.3.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.3.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.4.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.4.17
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.4.20
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.4.24
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.4.26
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.4.29
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.4.33
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.4.35
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.4.37
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.4.38
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.4.39
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.4.40
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.4.42
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.4.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.0.4.7
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.1.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.2.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.3.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.4.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.5.10
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.5.12
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.5.15
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.5.16
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.5.19
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.5.21
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.6.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.6.10
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.6.11
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.6.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.6.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.6.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.7
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.7.11
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.7.12
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.7.13
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.7.15
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.7.16
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.7.19
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.7.20
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.7.21
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.7.23
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.7.25
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.7.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.7.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.7.7
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.1.7.9
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.10.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.10.1.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.0.0
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.0.104
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.2.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.2.7
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.2.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.3.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.3.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.3.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.4.10
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.4.13
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.4.14
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.4.16
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.4.17
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.4.18
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.4.19
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.4.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.4.20
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.4.22
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.4.24
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.4.25
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.4.27
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.4.28
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.4.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.4.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.2.4.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.3.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.3.1.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.3.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.3.2.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.3.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.3.3.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.3.3.10
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.3.3.11
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.3.3.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.3.3.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.3.3.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.3.3.7
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.3.3.9
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.3.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.0.115
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.1.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.1.13
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.1.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.1.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.1.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.1.7
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.1.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.2.11
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.2.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.2.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.3.11
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.3.12
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.3.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.3.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.3.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.3.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.4.10
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.4.12
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.4.13
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.4.14
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.4.16
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.4.17
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.4.18
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.4.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.4.20
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.4.22
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.4.24
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.4.25
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.4.27
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.4.28
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.4.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.4.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.4.4.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.5.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.5.1.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.5.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.5.2.10
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.5.2.14
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.5.2.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.5.2.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.5.2.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.5.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.5.3.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.5.3.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.5.3.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.5.3.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.5.3.9
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.0
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.1.10
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.1.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.1.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.2.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.2.11
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.2.13
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.2.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.2.22
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.2.23
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.2.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.2.7
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.2.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.2.9
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.3.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.3.11
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.3.12
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.3.14
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.3.17
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.3.20
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.3.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.3.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.3.9
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.4.10
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.4.12
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.4.14
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.4.17
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.4.18
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.4.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.4.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.4.6
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.6.4.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.62.22
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.62.23
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.63.20
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.7.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.7.1.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.7.1.15
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.7.1.16
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.7.1.19
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.7.1.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.7.1.20
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.7.1.21
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.7.1.23
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.7.1.24
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.7.1.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.7.1.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.1.5
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.1.7
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.2.10
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.2.11
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.2.14
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.2.15
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.2.17
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.2.18
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.2.19
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.2.20
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.2.24
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.2.26
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.2.28
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.2.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.2.33
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.2.35
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.2.38
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.2.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.3.11
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.3.14
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.3.16
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.8.3.8
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.9.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.9.1.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.9.1.3
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.9.1.4
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.9.2
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.9.2.1
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.9.2.14
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.9.2.18
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.9.2.25
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.9.2.27
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.9.2.32
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Behoben9.9.2.9
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - BehobenBase
Cisco has released software updates that address this vulnerability.
https://software.cisco.com - Workaround7.0.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.1.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.4.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.5.12
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.6.18
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.6.22
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.6.26
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.6.29
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.6.32
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.6.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.6.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.7
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.7.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.7.12
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.7.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.7.9
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.8.12
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.8.13
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.8.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.0.8.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.1.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.1.2.16
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.1.2.20
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.1.2.24
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.1.2.28
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.1.2.38
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.1.2.42
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.1.2.46
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.1.2.49
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.1.2.53
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.1.2.61
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.1.2.64
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.1.2.72
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.1.2.81
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.1.13
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.1.19
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.1.24
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.1.9
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.2.10
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.2.14
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.2.18
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.2.19
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.2.22
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.2.34
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.2.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.3.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.3.12
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.3.16
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.4.18
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.4.25
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.4.27
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.4.30
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.4.33
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.4.42
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.4.46
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.4.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.4.9
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.5.10
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.5.12
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.5.16
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.5.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.5.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.5.7
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround7.2.5.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.1.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.2.11
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.2.15
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.3.12
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.3.19
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.3.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.4.16
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.4.23
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.4.25
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.4.28
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.4.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.4.31
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.4.32
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.4.33
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.4.38
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.4.39
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.4.44
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.4.9
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.5.20
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.5.23
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.5.25
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.5.27
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.5.28
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.0.5.31
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.1.0.104
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.1.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.1.1.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.1.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.1.2.13
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.1.2.15
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.1.2.16
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.1.2.19
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.1.2.23
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.1.2.24
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.1.2.49
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.1.2.50
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.1.2.55
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.1.2.56
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.0.45
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.1.11
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.2.10
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.2.12
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.2.16
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.2.17
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.2.9
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.4.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.4.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.5.13
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.5.22
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.5.26
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.5.33
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.5.40
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.5.41
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.5.46
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.5.48
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.5.49
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.5.50
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.5.51
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.5.52
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.5.55
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.5.57
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.5.58
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.2.5.59
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.3.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.3.1.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.3.1.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.3.1.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.3.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.3.2.13
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.3.2.23
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.3.2.25
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.3.2.31
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.3.2.33
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.3.2.34
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.3.2.37
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.3.2.39
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.3.2.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.3.2.40
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.3.2.41
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.3.2.44
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.1.11
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.1.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.2.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.2.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.3.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.3.9
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.4.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.4.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.4.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.4.9
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.5.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.6.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.7
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.7.15
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.7.22
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.7.23
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.7.26
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.7.28
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.7.29
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.7.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.7.30
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.4.7.31
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.5.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.5.1.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.5.1.14
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.5.1.17
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.5.1.18
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.5.1.19
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.5.1.21
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.5.1.24
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.5.1.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.5.1.7
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.6.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.6.1.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.6.1.10
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.6.1.12
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.6.1.13
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.6.1.14
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.6.1.15
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.6.1.17
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.6.1.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.6.1.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.7.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.7.1.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.7.1.11
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.7.1.13
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.7.1.16
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.7.1.17
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.7.1.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.7.1.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.7.1.7
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround8.7.1.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.2.10
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.3.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.3.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.4.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.4.17
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.4.20
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.4.24
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.4.26
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.4.29
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.4.33
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.4.35
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.4.37
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.4.38
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.4.39
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.4.40
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.4.42
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.4.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.0.4.7
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.1.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.2.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.3.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.4.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.5.10
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.5.12
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.5.15
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.5.16
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.5.19
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.5.21
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.6.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.6.10
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.6.11
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.6.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.6.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.6.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.7
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.7.11
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.7.12
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.7.13
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.7.15
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.7.16
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.7.19
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.7.20
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.7.21
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.7.23
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.7.25
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.7.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.7.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.7.7
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.1.7.9
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.10.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.10.1.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.0.0
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.0.104
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.2.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.2.7
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.2.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.3.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.3.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.3.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.4.10
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.4.13
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.4.14
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.4.16
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.4.17
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.4.18
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.4.19
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.4.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.4.20
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.4.22
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.4.24
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.4.25
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.4.27
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.4.28
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.4.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.4.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.2.4.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.3.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.3.1.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.3.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.3.2.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.3.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.3.3.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.3.3.10
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.3.3.11
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.3.3.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.3.3.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.3.3.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.3.3.7
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.3.3.9
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.3.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.0.115
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.1.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.1.13
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.1.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.1.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.1.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.1.7
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.1.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.2.11
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.2.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.2.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.3.11
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.3.12
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.3.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.3.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.3.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.3.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.4.10
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.4.12
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.4.13
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.4.14
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.4.16
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.4.17
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.4.18
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.4.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.4.20
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.4.22
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.4.24
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.4.25
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.4.27
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.4.28
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.4.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.4.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.4.4.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.5.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.5.1.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.5.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.5.2.10
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.5.2.14
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.5.2.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.5.2.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.5.2.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.5.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.5.3.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.5.3.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.5.3.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.5.3.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.5.3.9
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.0
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.1.10
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.1.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.1.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.2.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.2.11
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.2.13
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.2.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.2.22
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.2.23
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.2.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.2.7
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.2.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.2.9
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.3.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.3.11
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.3.12
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.3.14
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.3.17
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.3.20
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.3.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.3.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.3.9
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.4.10
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.4.12
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.4.14
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.4.17
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.4.18
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.4.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.4.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.4.6
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.6.4.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.62.22
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.62.23
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.63.20
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.7.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.7.1.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.7.1.15
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.7.1.16
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.7.1.19
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.7.1.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.7.1.20
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.7.1.21
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.7.1.23
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.7.1.24
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.7.1.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.7.1.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.1.5
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.1.7
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.2.10
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.2.11
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.2.14
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.2.15
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.2.17
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.2.18
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.2.19
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.2.20
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.2.24
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.2.26
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.2.28
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.2.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.2.33
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.2.35
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.2.38
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.2.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.3.11
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.3.14
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.3.16
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.8.3.8
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.9.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.9.1.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.9.1.3
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.9.1.4
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.9.2
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.9.2.1
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.9.2.14
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.9.2.18
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.9.2.25
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.9.2.27
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.9.2.32
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- Workaround9.9.2.9
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
- WorkaroundBase
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
Advisories wie diese benennen die exponierten Produkte, die Angreifer auf Ihrer Angriffsfläche ins Visier nehmen. Sehen Sie mit einem kostenlosen Passiv-Scan, was exponiert ist.
Kostenloser Scan