Adaptive Security Appliance SoftwareOperating system · Cisco

CVE-2024-20485

MEDIUM · 6.7 CVSS v3.1 Published 2024-10-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability in the VPN web server of Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an authenticated, local attacker to execute arbitrary code with root-level privileges. Administrator-level privileges are required to exploit this vulnerability. This vulnerability is due to improper validation of a specific file when it is read from system flash memory. An attacker could exploit this vulnerability by restoring a crafted backup file to an affected device. A successful exploit could allow the attacker to execute arbitrary code on the affected device after the next reload of the device, which could alter system behavior. Because the injected code could persist across device reboots, Cisco has raised the Security Impact Rating (SIR) of this advisory from Medium to High.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A vulnerability in the VPN web server of Cisco ASA and FTD Software allows an authenticated attacker with administrator privileges to execute arbitrary code with root-level privileges by restoring a crafted backup file to the device. The vulnerability stems from improper validation of a specific file read from system flash memory, and successful exploitation results in persistent code execution across device reboots.

MitigationApply the vendor-supplied patches for Cisco ASA and FTD Software when available. Restrict administrative access to trusted personnel and validate any backup files before restoration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Adaptive Security Appliance SoftwareOperating system
Affected:= 9.8.1= 9.8.1.5= 9.8.1.7= 9.8.2= 9.8.2.8= 9.8.2.14= 9.8.2.15= 9.8.2.17= 9.8.2.20= 9.8.2.24= 9.8.2.26= 9.8.2.28
Secure Firewall Threat DefenseApplication
Affected:= 6.2.3= 6.2.3.1= 6.2.3.2= 6.2.3.3= 6.2.3.4= 6.2.3.5= 6.2.3.6= 6.2.3.7= 6.2.3.8= 6.2.3.9= 6.2.3.10= 6.2.3.11

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify device product and software version
    Execute 'show version' or 'show running-config | include version' via CLI to retrieve the Cisco ASA or FTD software version
    Affected if The installed version matches any version listed in the affected versions: ASA 9.8.1, 9.8.1.5, 9.8.1.7, 9.8.2, 9.8.2.8, 9.8.2.14, 9.8.2.15, 9.8.2.17, 9.8.2.20, 9.8.2.24, 9.8.2.26, 9.8.2.28 or FTD 6.2.3 through 6.2.3.11
  2. Verify administrator account access
    Check 'show privilege' or review 'show running-config | include username' to identify accounts with administrator privileges
    Affected if Any administrator-level user accounts exist on the device, as exploitation requires administrator privileges to restore a backup file
  3. Audit recent configuration backup restorations
    Review 'show archive' logs, system messages, or check the device flash for recently modified backup configuration files using 'dir /recursive'
    Affected if A crafted backup file was recently restored to the device, which would indicate attempted or successful exploitation

The device is affected if it runs Cisco ASA Software version 9.8.1 through 9.8.2.28 or FTD Software version 6.2.3 through 6.2.3.11, has the VPN web server enabled, and allows administrator-level access for backup file restoration.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied patches for Cisco ASA and FTD Software when available. Restrict administrative access to trusted personnel and validate any backup files before restoration.

Recommended fix Moderate confidence

Upgrade to the fixed ASA Software release (9.8.x or later fixed release) and/or FTD Software release (6.2.3.x or later fixed release) as specified in the Cisco security advisory

  1. 1. Verify the current software version on the Cisco ASA or FTD device using the 'show version' command
  2. 2. Access the Cisco Security Advisory at sec.cloudapps.cisco.com for CVE-2024-20485 to obtain the specific fixed software release numbers
  3. 3. Download the recommended fixed version from the Cisco Software Download center
  4. 4. Plan a maintenance window as the exploit requires device reload to take effect
  5. 5. Back up the current device configuration
  6. 6. Upgrade the ASA Software or FTD Software to the fixed release version
  7. 7. After upgrade, verify the new version is installed using 'show version'
  8. 8. Confirm the vulnerability is remediated by attempting the documented attack vector (backup file restore) or verify with Cisco's remediation verification steps
Caveat Review Cisco's release notes for the target version for any configuration or compatibility changes; some features may behave differently in newer releases

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Adaptive Security Appliance Software Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20485 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-20485 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data