CVE intelligence and bounded remediation
CVE-2018-0227 — Cisco Adaptive Security Appliance Software security vulnerability
A vulnerability in the Secure Sockets Layer (SSL) Virtual Private Network (VPN) Client Certificate Authentication feature for Cisco Adaptive Security Appliance (ASA) could allow an unauthenticated, remote attacker to establish an SSL VPN connection and bypass certain SSL certificate verification steps. The vulnerability is due to incorrect verification of the SSL Client Certificate. An attacker could exploit this vulnerability by connecting to the ASA VPN without a proper private key and certificate pair. A successful exploit could allow the attacker to establish an SSL VPN connection to the ASA when the connection should have been rejected. This vulnerability affects Cisco Adaptive Security Appliance (ASA) and Firepower Threat Defense (FTD) Software that is running on the following Cisco products: 3000 Series Industrial Security Appliances (ISA), ASA 5500 Series Adaptive Security Appliances, ASA 5500-X Series Next-Generation Firewalls, ASA Services Module for Cisco Catalyst 6500 Series Switches and Cisco 7600 Series Routers, Adaptive Security Virtual Appliances (ASAv), Firepower 4110 Security Appliances, Firepower 9300 ASA Security Modules. Cisco Bug IDs: CSCvg40155.
- Severity
- High
- CVSS
- 7.5 (3.1)
- Published
- 2018-04-19
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-295
Affected products
- cisco / adaptive_security_appliance_software
- cisco / adaptive_security_appliance_software / 9.4.3.1
- cisco / adaptive_security_appliance_software / 9.4.3.2
- cisco / adaptive_security_appliance_software / 9.5.2.7
- cisco / adaptive_security_appliance_software / 9.5.2.8
- cisco / firepower_threat_defense
Matched remediation archetype
Cryptography, certificate, signature, and channel validation
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Inventory affected algorithms, key uses, trust stores, certificate validation settings, random sources, and plaintext channels across clients and services.
- Determine which secrets, identities, signatures, or data protections depend on the affected primitive or validation path.
- Check debug, compatibility, fallback, and hostname or audience override settings in build and runtime configuration.
Remediate safely
- Use a maintained platform cryptographic API with approved algorithms, modes, parameters, randomness, and full peer identity validation.
- Remove insecure fallback and validation bypasses; separate keys by purpose and load them from managed secret storage.
- Plan rotation or reissuance for affected keys, certificates, tokens, hashes, or ciphertext and document compatibility sequencing.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.