CVE-2022-20927
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 the SSL/TLS client of Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an authenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. This vulnerability is due to improper memory management when a device initiates SSL/TLS connections. An attacker could exploit this vulnerability by ensuring that the device will connect to an SSL/TLS server that is using specific encryption parameters. A successful exploit could allow the attacker to cause the affected device to unexpectedly reload, resulting in a DoS condition.
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 memory management vulnerability exists in the SSL/TLS client of Cisco ASA and FTD software. When the device initiates SSL/TLS connections to a server using specific encryption parameters, improper memory handling causes the device to unexpectedly reload, resulting in 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.13.1= 9.13.1.2= 9.13.1.7= 9.13.1.10= 9.13.1.12= 9.13.1.13= 9.13.1.16= 9.13.1.19= 9.13.1.21= 9.14.1= 9.14.1.10= 9.14.1.15>= 6.5.0, <= 6.5.0.5>= 6.7.0, <= 6.7.0.3= 6.6.0= 6.6.0.1= 6.6.1= 6.6.3= 6.6.4= 6.6.5= 6.6.5.1all versionsCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 product and versionRun 'show version' on the device CLI to obtain the software version and model informationAffected if The device runs Cisco ASA Software, Cisco FTD, or Firepower Services for ASA and the version matches the affected list (9.13.1.x, 9.14.1.x for ASA; 6.5.0-6.5.0.5, 6.6.0-6.6.5.1, 6.7.0-6.7.0.3 for FTD; any version for Firepower Services for ASA)
-
Confirm the SSL/TLS client feature is in useReview the device configuration for any crypto ssl commands (ASA) or SSL/TLS inspection policies, or check for outbound SSL/TLS connections to remote servers using 'show crypto ssl' or related commandsAffected if The device is configured to initiate SSL/TLS connections to external servers (the vulnerability only affects the SSL/TLS client side, not server side)
-
Verify crypto/SSL configurationUse 'show run crypto ssl' or examine the SSL VPN or SSL inspection configuration to see which encryption parameters and cipher suites are configuredAffected if Specific encryption parameters are in use when the device acts as an SSL/TLS client connecting to servers; the exact parameters triggering the flaw are defined in the Cisco advisory
The environment is affected if the device runs an affected ASA or FTD version (or any version of Firepower Services for ASA) AND the SSL/TLS client feature is actively used to initiate connections to servers with vulnerable encryption parameters.
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 update/patch for CVE-2022-20927 to affected ASA and FTD deployments. Until the patch is available, restrict outbound SSL/TLS connections from the device to trusted servers only.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-20927 — 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-20927 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