SECUFOCUSNOW
Home›Remediation guides›CVE-2018-0175
CVE REMEDIATION GUIDE
CISA KEV · Known exploitedHighResearch in progress

CVE-2018-0175 remediation guide

Cisco IOS, XR, and XE Software

Format String vulnerability in the Link Layer Discovery Protocol (LLDP) subsystem of Cisco IOS Software, Cisco IOS XE Software, and Cisco IOS XR Software could allow an unauthenticated, adjacent attacker to cause a denial of service (DoS) condition or execute arbitrary code with elevated privileges on an affected device. Cisco Bug IDs: CSCvd73664.

Open CVE record
Research in progress

A verified fixed-version field is not available. Use the linked NVD and supporting references, then confirm the vendor-supported path before changing production systems.

ProductCisco IOS, XR, and XE Software
Affected versionsCisco IOS, IOS XE, and IOS XR, 15.4(3)m4.1, <= 15.2\(4a\)ea5, <= 15.2\(6\)e0a, <= 15.6.3m1
Fixed versionsNo verified fixed-version field is available yet
Priority basisImmediate · CVSS 8 · EPSS 3.50%
01

Identify the affected asset

Confirm whether Cisco IOS, XR, and XE Software 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 IOS, IOS XE, and IOS XR, 15.4(3)m4.1, <= 15.2\(4a\)ea5, <= 15.2\(6\)e0a, <= 15.6.3m1. Treat incomplete inventory results as unresolved.

03

Prioritize with independent signals

CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.

04

Apply supported remediation

Apply updates per vendor instructions.

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.