CVE-2018-15465

mediumpriority · track · 33OT risk · elevatedEPSS 0.024 · 84 %ileEURUUS

grimoire priorityP3 · Track

Exploitable?

—

no known exploitation

Likely / severe?

2.38% (84th) EPSS

CVSS 5.5 · medium

Is it mine?

473 products

Check your exposure

Who says so?

4 sources

cnnvd · enisa_euvd · fstec_bdu · cisco_csaf

EPSS · scored 2026-10-27

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.

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

A vendor fix is available.

Fixed7.0.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.1.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.4.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.5.12cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.6.18cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.6.22cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.6.26cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.6.29cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.6.32cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.6.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.6.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.7cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.7.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.7.12cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.7.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.7.9cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.8.12cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.8.13cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.8.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.0.8.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.1.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.1.2.16cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.1.2.20cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.1.2.24cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.1.2.28cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.1.2.38cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.1.2.42cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.1.2.46cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.1.2.49cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.1.2.53cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.1.2.61cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.1.2.64cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.1.2.72cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.1.2.81cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.1.13cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.1.19cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.1.24cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.1.9cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.2.10cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.2.14cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.2.18cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.2.19cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.2.22cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.2.34cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.2.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.3.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.3.12cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.3.16cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.4.18cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.4.25cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.4.27cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.4.30cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.4.33cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.4.42cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.4.46cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.4.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.4.9cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.5.10cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.5.12cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.5.16cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.5.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.5.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.5.7cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed7.2.5.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.1.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.2.11cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.2.15cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.3.12cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.3.19cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.3.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.4.16cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.4.23cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.4.25cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.4.28cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.4.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.4.31cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.4.32cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.4.33cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.4.38cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.4.39cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.4.44cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.4.9cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.5.20cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.5.23cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.5.25cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.5.27cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.5.28cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.0.5.31cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.1.0.104cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.1.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.1.1.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.1.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.1.2.13cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.1.2.15cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.1.2.16cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.1.2.19cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.1.2.23cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.1.2.24cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.1.2.49cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.1.2.50cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.1.2.55cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.1.2.56cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.0.45cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.1.11cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.2.10cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.2.12cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.2.16cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.2.17cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.2.9cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.4.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.4.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.5.13cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.5.22cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.5.26cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.5.33cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.5.40cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.5.41cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.5.46cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.5.48cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.5.49cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.5.50cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.5.51cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.5.52cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.5.55cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.5.57cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.5.58cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.2.5.59cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.3.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.3.1.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.3.1.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.3.1.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.3.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.3.2.13cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.3.2.23cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.3.2.25cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.3.2.31cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.3.2.33cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.3.2.34cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.3.2.37cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.3.2.39cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.3.2.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.3.2.40cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.3.2.41cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.3.2.44cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.1.11cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.1.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.2.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.2.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.3.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.3.9cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.4.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.4.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.4.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.4.9cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.5.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.6.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.7cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.7.15cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.7.22cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.7.23cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.7.26cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.7.28cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.7.29cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.7.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.7.30cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.4.7.31cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.5.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.5.1.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.5.1.14cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.5.1.17cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.5.1.18cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.5.1.19cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.5.1.21cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.5.1.24cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.5.1.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.5.1.7cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.6.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.6.1.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.6.1.10cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.6.1.12cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.6.1.13cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.6.1.14cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.6.1.15cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.6.1.17cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.6.1.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.6.1.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.7.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.7.1.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.7.1.11cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.7.1.13cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.7.1.16cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.7.1.17cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.7.1.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.7.1.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.7.1.7cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed8.7.1.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.2.10cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.3.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.3.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.4.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.4.17cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.4.20cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.4.24cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.4.26cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.4.29cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.4.33cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.4.35cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.4.37cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.4.38cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.4.39cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.4.40cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.4.42cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.4.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.0.4.7cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.1.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.2.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.3.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.4.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.5.10cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.5.12cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.5.15cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.5.16cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.5.19cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.5.21cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.6.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.6.10cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.6.11cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.6.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.6.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.6.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.7cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.7.11cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.7.12cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.7.13cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.7.15cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.7.16cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.7.19cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.7.20cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.7.21cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.7.23cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.7.25cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.7.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.7.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.7.7cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.1.7.9cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.10.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.10.1.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.0.0cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.0.104cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.2.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.2.7cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.2.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.3.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.3.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.3.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.4.10cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.4.13cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.4.14cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.4.16cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.4.17cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.4.18cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.4.19cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.4.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.4.20cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.4.22cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.4.24cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.4.25cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.4.27cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.4.28cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.4.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.4.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.2.4.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.3.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.3.1.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.3.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.3.2.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.3.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.3.3.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.3.3.10cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.3.3.11cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.3.3.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.3.3.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.3.3.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.3.3.7cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.3.3.9cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.3.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.0.115cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.1.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.1.13cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.1.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.1.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.1.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.1.7cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.1.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.2.11cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.2.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.2.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.3.11cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.3.12cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.3.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.3.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.3.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.3.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.4.10cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.4.12cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.4.13cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.4.14cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.4.16cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.4.17cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.4.18cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.4.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.4.20cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.4.22cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.4.24cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.4.25cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.4.27cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.4.28cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.4.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.4.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.4.4.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.5.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.5.1.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.5.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.5.2.10cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.5.2.14cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.5.2.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.5.2.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.5.2.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.5.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.5.3.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.5.3.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.5.3.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.5.3.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.5.3.9cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.0cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.1.10cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.1.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.1.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.2.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.2.11cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.2.13cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.2.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.2.22cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.2.23cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.2.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.2.7cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.2.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.2.9cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.3.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.3.11cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.3.12cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.3.14cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.3.17cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.3.20cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.3.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.3.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.3.9cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.4.10cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.4.12cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.4.14cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.4.17cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.4.18cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.4.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.4.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.4.6cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.6.4.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.62.22cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.62.23cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.63.20cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.7.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.7.1.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.7.1.15cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.7.1.16cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.7.1.19cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.7.1.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.7.1.20cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.7.1.21cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.7.1.23cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.7.1.24cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.7.1.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.7.1.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.1.5cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.1.7cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.10cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.11cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.14cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.15cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.17cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.18cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.19cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.20cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.24cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.26cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.28cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.33cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.35cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.38cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.2.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.3.11cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.3.14cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.3.16cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.8.3.8cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.1.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.1.3cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.1.4cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.2cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.2.1cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.2.14cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.2.18cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.2.25cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.2.27cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.2.32cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Fixed9.9.2.9cisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
FixedBasecisco_csaf
Cisco has released software updates that address this vulnerability.
https://software.cisco.com
Workaround7.0.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.12cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.18cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.22cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.26cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.29cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.32cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.7cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.12cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.9cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.12cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.13cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.16cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.20cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.24cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.28cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.38cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.42cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.46cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.49cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.53cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.61cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.64cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.72cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.81cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.13cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.19cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.24cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.9cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.10cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.14cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.18cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.19cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.22cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.34cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.12cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.16cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.18cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.25cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.27cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.30cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.33cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.42cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.46cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.9cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.10cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.12cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.16cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.7cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.11cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.15cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.12cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.19cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.16cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.23cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.25cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.28cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.31cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.32cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.33cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.38cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.39cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.44cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.9cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.20cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.23cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.25cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.27cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.28cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.31cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.104cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.13cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.15cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.16cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.19cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.23cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.24cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.49cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.50cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.55cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.56cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.45cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.11cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.10cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.12cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.16cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.17cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.9cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.13cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.22cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.26cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.33cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.40cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.41cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.46cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.48cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.49cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.50cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.51cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.52cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.55cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.57cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.58cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.59cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.13cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.23cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.25cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.31cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.33cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.34cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.37cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.39cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.40cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.41cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.44cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.11cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.9cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.9cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.7cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.15cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.22cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.23cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.26cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.28cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.29cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.30cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.31cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.14cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.17cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.18cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.19cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.21cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.24cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.7cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.10cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.12cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.13cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.14cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.15cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.17cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.11cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.13cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.16cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.17cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.7cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.10cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.17cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.20cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.24cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.26cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.29cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.33cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.35cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.37cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.38cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.39cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.40cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.42cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.7cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.10cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.12cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.15cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.16cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.19cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.21cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.10cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.11cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.7cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.11cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.12cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.13cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.15cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.16cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.19cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.20cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.21cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.23cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.25cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.7cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.9cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.0cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.104cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.7cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.10cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.13cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.14cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.16cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.17cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.18cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.19cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.20cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.22cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.24cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.25cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.27cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.28cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.10cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.11cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.7cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.9cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.115cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.13cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.7cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.11cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.11cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.12cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.10cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.12cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.13cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.14cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.16cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.17cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.18cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.20cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.22cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.24cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.25cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.27cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.28cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.10cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.14cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.9cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.0cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.10cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.11cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.13cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.22cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.23cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.7cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.9cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.11cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.12cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.14cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.17cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.20cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.9cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.10cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.12cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.14cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.17cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.18cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.6cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.22cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.23cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.20cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.15cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.16cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.19cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.20cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.21cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.23cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.24cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.5cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.7cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.10cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.11cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.14cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.15cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.17cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.18cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.19cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.20cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.24cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.26cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.28cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.33cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.35cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.38cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.11cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.14cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.16cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.8cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.3cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.4cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.2cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.1cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.14cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.18cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.25cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.27cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.32cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["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.9cisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].
WorkaroundBasecisco_csaf
Enabling command authorization prevents exploitation of this vulnerability. Notes Enabling command authorization significantly changes the way that the Cisco ASA interprets privilege levels and authorizes actions. Before enabling the feature, administrators must clearly define which actions are allowed per privilege level using the privilege command in global configuration mode. Administrators should not enable command authorization using the aaa authorization command command until they have defined these actions. Administrators who use the Adaptive Security Device Manager (ASDM) to manage the ASA are advised to enable command authorization by using the ASDM because doing so will allow the ASDM to push predefined command sets for different privilege levels to the ASA. Having these command sets in place will ensure proper ASDM operation after command authorization is enabled. Further information about command authorization is in the “Management Access” chapter of the “System Administration” section in Cisco ASA Series General Operations CLI Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/configuration/general/asa-910-general-config/admin-management.html#ID-2111-00000646"] and Cisco ASA Series General Operations ASDM Configuration Guide ["https://www.cisco.com/c/en/us/td/docs/security/asa/asa910/asdm710/general/asdm-710-general-config/admin-management.html#ID-2111-00000646"].

cvss

Technical severity, 0–10. One row per scoring source.

9.1

010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–critical · 5.5–9.1

v2.05.5mediumAV:N/AC:L/Au:S/C:P/I:P/A:Nprimary · NVD / NIST USexploitability 8 · impact 4.9

v3.08.1highCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Nprimary · NVD / NIST USexploitability 2.8 · impact 5.2

v3.08.1highCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Nsecondary · ENISA EU

v3.08.1highCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Nsecondary · Cisco PSIRT US

v3.08.1highCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Nsecondary · psirt@cisco.com USexploitability 2.8 · impact 5.2

v3.07.4highCVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N/E:Usecondary · CVSS-BT (t0sche)

v3.19.1criticalAV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:Nsecondary · FSTEC (BDU) RU

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Exploitation: none · Automatable: no · Technical Impact: totalcoordinatorcisa_ssvcUS

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-863USprimaryCWE-285USCWE-285US

affected products (473)

Products and version ranges known to be affected.

showing 20 of 473

advisories (1)

Vendor and ecosystem advisories describing this.

cisco-sa-20181219-asa-privescCisco Adaptive Security Appliance Software Privilege Escalation Vulnerability2018-12-19csaf · cisco_csafUS
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.

also known as (4)

Other names and identifiers for this entity.

sources

Which sources assert this record, and when.

cnnvd enisa_euvd fstec_bdu cisco_csaf NVD CVE.org MITRE

published 2018-12-24modified 2026-06-17

related (5,011)

Related entries.

ID	severity	EPSS	exploitable	published
CVE-2026-71362US	—OT critical	90.5% (100th)	KEV	2026-08-11
Adobe Commerce is affected by an Incorrect Authorization vulnerability that could result in privilege escalation. An attacker could leverage this vulnerability to gain elevated acc…
CVE-2026-42016US	high8.8OT critical	8.64% (95th)	KEV	2026-07-27
JFrog Artifactory (Self Hosted) versions before 7.133.11 are vulnerable to a privilege escalation attack due to a validation check of the token signature/issuer and not the token’s…
CVE-2025-55177US	—OT critical	13.1% (96th)	KEV	2025-08-29
Incomplete authorization of linked device synchronization messages in WhatsApp for iOS prior to v2.25.21.73, WhatsApp Business for iOS v2.25.21.78, and WhatsApp for Mac v2.25.21.78…
CVE-2025-54253US	—OT critical	88.8% (100th)	KEV	2025-08-05
Adobe Experience Manager versions 6.5.23 and earlier are affected by a Misconfiguration vulnerability that could result in arbitrary code execution. An attacker could leverage this…
CVE-2025-21479US	—OT critical	0.84% (58th)	KEV	2025-06-03
Memory corruption due to unauthorized command execution in GPU micronode while executing specific sequence of commands.

+5006 more

references (9)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan