CVE intelligence and bounded remediation

CVE-2024-20341 — Cisco Adaptive Security Appliance Software security vulnerability

Medium CVSS 6.1

A vulnerability in the VPN web client services feature of Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a browser that is accessing an affected device. This vulnerability is due to improper validation of user-supplied input to application endpoints. An attacker could exploit this vulnerability by persuading a user to follow a link designed to submit malicious input to the affected application. A successful exploit could allow the attacker to execute arbitrary HTML or script code in the browser in the context of the web services page.

Severity
Medium
CVSS
6.1 (3.1)
Published
2024-10-23
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-80, CWE-79

Affected products

  • cisco / adaptive_security_appliance_software / 9.8.1
  • cisco / adaptive_security_appliance_software / 9.8.1.5
  • cisco / adaptive_security_appliance_software / 9.8.1.7
  • cisco / adaptive_security_appliance_software / 9.8.2
  • cisco / adaptive_security_appliance_software / 9.8.2.8
  • cisco / adaptive_security_appliance_software / 9.8.2.14

Showing 6 representative product identities from 272 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Cross-site scripting and unsafe browser output

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace reflected, stored, and DOM-derived untrusted values into HTML, attributes, URLs, styles, scripts, and client-side template sinks.
  • Identify affected origins, authenticated user roles, sensitive browser capabilities, and where content is shared across tenants.
  • Review framework escaping, rich-text sanitization, legacy templates, and client-side rendering paths.

Remediate safely

  • Use context-aware framework output encoding and safe DOM APIs; keep untrusted data out of executable contexts.
  • Sanitize intentionally supported markup with a maintained allowlist policy and validate URLs and attributes separately.
  • Update affected rendering components and add tests for every output context using inert sentinel markup.

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.