CVE REMEDIATION GUIDE
Review reviewHighFixed-version data available

CVE-2018-0231 remediation guide

Cisco Adaptive Security Appliance, adaptive security appliance software, secure firewall threat defense

A vulnerability in the Transport Layer Security (TLS) library of Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to trigger a reload of the affected device, resulting in a denial of service (DoS) condition. The vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by sending a malicious TLS message to an interface enabled for Secure Layer Socket (SSL) services on an affected device. Messages using SSL Version 3 (SSLv3) or SSL Versi...

Open CVE record
ProductCisco Adaptive Security Appliance, adaptive security appliance software, secure firewall threat defense
Affected versions>= Cisco Adaptive Security Appliance, 9.8(1), 98.1(1.154), >= 6.0 < 6.1.0.6, >= 6.2.1 < 6.2.2.1
Fixed versions6.1.0.6, 6.2.2.1
Priority basisReview · CVSS 8.6 · EPSS 4.60%
01

Identify the affected asset

Confirm whether Cisco Adaptive Security Appliance, adaptive security appliance software, secure firewall threat defense is installed, record the deployed version and installation path, and identify exposed interfaces.

  • Record the product name, package or appliance identifier, and installed version.
  • Identify internet-facing, administrative, API, and internal access paths.
  • Preserve the pre-change configuration and relevant service logs.
02

Validate the affected-version match

Compare the deployed version with the affected range: >= Cisco Adaptive Security Appliance, 9.8(1), 98.1(1.154), >= 6.0 < 6.1.0.6, >= 6.2.1 < 6.2.2.1. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

The CVSS severity warrants an early asset and exposure review. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Follow the vendor advisory or supported update path. Current fixed-version status: 6.1.0.6, 6.2.2.1. Preserve configuration and rollback material before change.

05

Verify the result

Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.

  • Confirm the expected version and package state.
  • Run a functional health check for critical service paths.
  • Review authentication, error, application, and security monitoring logs.
  • Reassess exposure if the supported fix cannot be applied.

Operational boundary

This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.