CVE-2022-20947
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 · uneditedA vulnerability in dynamic access policies (DAP) functionality of Cisco Adaptive Security Appliance (ASA) Software and Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause an affected device to reload, resulting in a denial of service (DoS) condition. This vulnerability is due to improper processing of HostScan data received from the Posture (HostScan) module. An attacker could exploit this vulnerability by sending crafted HostScan data to an affected device. A successful exploit could allow the attacker to cause the affected device to reload, resulting in a DoS condition. https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asa-ftd-dap-dos-GhYZBxDU ["https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-asa-ftd-dap-dos-GhYZBxDU"] This advisory is part of the November 2022 release of the Cisco ASA, FTD, and FMC Security Advisory Bundled publication.
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 · high confidenceA vulnerability in the Dynamic Access Policies (DAP) feature of Cisco ASA and FTD software allows an unauthenticated remote attacker to cause device reload by sending crafted HostScan data. The vulnerability exists due to improper processing of HostScan data received from the Posture (HostScan) module, leading to denial of service.
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= 9.6.1= 9.6.1.3= 9.6.1.5= 9.6.1.10= 9.6.2= 9.6.2.1= 9.6.2.2= 9.6.2.3= 9.6.2.7= 9.6.2.11= 9.6.2.13= 9.6.2.22= 6.1.0= 6.1.0.1= 6.1.0.2= 6.1.0.3= 6.1.0.4= 6.1.0.5= 6.1.0.6= 6.1.0.7= 6.2.0= 6.2.0.1= 6.2.0.2= 6.2.0.3CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Cisco device product typeRun 'show version' or check the system prompt to determine if the device is running Cisco ASA or Firepower Threat Defense (FTD) software.Affected if Device is running ASA or FTD software and matches the affected versions listed.
-
Verify the software version against affected releasesRun 'show version' to obtain the exact software version number. Compare it to the CVE-affected versions: ASA versions 9.6.1 through 9.6.2.22 (specific builds listed), and FTD versions 6.1.0 through 6.2.0.3 (specific builds listed).Affected if The installed version exactly matches one of the listed affected versions.
-
Confirm Dynamic Access Policies (DAP) feature is configuredRun 'show dap session' or 'show running-config dap' to check if any DAP policies are defined on the device.Affected if DAP policies are actively configured on the device.
-
Verify Posture (HostScan) module is enabledRun 'show running-config all | include hostscan' or check the AnyConnect profile configuration to determine if the HostScan/Posture module is enabled for endpoint posture assessment.Affected if HostScan or Posture module is enabled and accepting connections from clients.
-
Check for device reload events or crash indicatorsRun 'show crashinfo' or review the system logs for recent unexpected reload events or process failures related to DAP or HostScan.Affected if Device has recently reloaded or crashed with no other clear cause, or crash logs reference dap or hostscan processes.
The device is affected if it runs an ASA or FTD version exactly matching one of the listed versions, has DAP configured, and has the HostScan/Posture module enabled.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply the relevant Cisco security patch from the November 2022 advisory. Until patched, restrict network access to interfaces handling HostScan connections and monitor for indicators of exploitation.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20947 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-20947 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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