CVE-2023-20107
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 deterministic random bit generator (DRBG), also known as pseudorandom number generator (PRNG), in Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software for Cisco ASA 5506-X, ASA 5508-X, and ASA 5516-X Firewalls could allow an unauthenticated, remote attacker to cause a cryptographic collision, enabling the attacker to discover the private key of an affected device. This vulnerability is due to insufficient entropy in the DRBG for the affected hardware platforms when generating cryptographic keys. An attacker could exploit this vulnerability by generating a large number of cryptographic keys on an affected device and looking for collisions with target devices. A successful exploit could allow the attacker to impersonate an affected target device or to decrypt traffic secured by an affected key that is sent to or from an affected target device.
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 confidenceA vulnerability in the deterministic random bit generator (DRBG) of Cisco ASA and FTD software for specific firewall models (5506-X, 5508-X, 5516-X) allows discovery of private keys due to insufficient entropy in the PRNG, enabling cryptographic collisions that permit device impersonation and traffic decryption.
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.12.1< 6.4.0CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 firewall modelRun 'show version' or 'show inventory' on the device CLI to confirm the exact model numberAffected if The model is NOT one of: 5506-X, 5508-X, or 5516-X (these are the only affected models)
-
Check Cisco ASA software versionRun 'show version' and locate the 'ASA' or 'Adaptive Security Appliance' software version lineAffected if The ASA version is 9.12.1 or higher (versions below 9.12.1 are affected)
-
Check Cisco FTD software versionRun 'show version' and locate the 'Firepower Threat Defense' or 'FTD' software version lineAffected if The FTD version is 6.4.0 or higher (versions below 6.4.0 are affected)
-
Confirm the device performs cryptographic operationsVerify the device is actively using VPN, SSL inspection, or certificate-based authentication by reviewing 'show run' or current configurationAffected if The device uses any cryptographic functions (VPN, SSL decryption, certificates) - this is required for the vulnerability to be exploitable in practice
You are affected if your device is a 5506-X, 5508-X, or 5516-X model running ASA version below 9.12.1 or FTD version below 6.4.0, and the device is performing cryptographic operations such as VPN or SSL inspection.
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.
dbcve · scoped6.4.09.12.1
Apply Cisco security updates for ASA/FTD software to address the entropy weakness; if patches are unavailable, consider network segmentation and monitoring for signs of impersonation attacks.
Cisco ASA 9.12.1 or later; Cisco FTD 6.4.0 or later
- Identify the current version of Cisco ASA Software or FTD Software running on the affected devices (ASA 5506-X, ASA 5508-X, ASA 5516-X).
- For Cisco ASA Software: Upgrade to version 9.12.1 or later.
- For Cisco Firepower Threat Defense Software: Upgrade to version 6.4.0 or later.
- Verify the upgrade was successful by confirming the new software version is installed.
- After upgrade, regenerate any cryptographic keys that were generated while running the vulnerable software version to ensure new keys use proper entropy.
- Consult Cisco ASA and FTD upgrade guides for any required migration steps or compatibility checks before upgrading.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation12.0 h
- Implementation20.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $13,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-20107 — 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-2023-20107 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