CVE intelligence and bounded remediation

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

Medium CVSS 6.8

A vulnerability in the session authentication functionality of the Remote Access SSL VPN feature of Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to prevent users from authenticating. This vulnerability is due to insufficient entropy in the authentication process. An attacker could exploit this vulnerability by determining the handle of an authenticating user and using it to terminate their authentication session. A successful exploit could allow the attacker to force a user to restart the authentication process, preventing a legitimate user from establishing remote access VPN sessions.

Severity
Medium
CVSS
6.8 (3.1)
Published
2024-10-23
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-330, CWE-331

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

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.