Adaptive Security Appliance SoftwareApplication · Cisco
CVE-2019-1695
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 detection engine of Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, adjacent attacker to send data directly to the kernel of an affected device. The vulnerability exists because the software improperly filters Ethernet frames sent to an affected device. An attacker could exploit this vulnerability by sending crafted packets to the management interface of an affected device. A successful exploit could allow the attacker to bypass the Layer 2 (L2) filters and send data directly to the kernel of the affected device. A malicious frame successfully delivered would make the target device generate a specific syslog entry.
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 detection engine of Cisco ASA and FTD software allows an unauthenticated adjacent attacker to bypass Layer 2 filtering by sending crafted Ethernet frames directly to the management interface. The improper filtering allows packets to reach the kernel, generating a specific syslog entry upon successful exploitation.
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 SoftwareApplication
< 9.8.4>= 9.9, < 9.9.2.50>= 9.10, < 9.10.1.17
Secure Firewall Threat DefenseApplication
>= 6.2.1, < 6.2.3.12>= 6.3.0, < 6.3.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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 product type and versionLog into the Cisco ASA or FTD device and run 'show version' or 'show version | include Version' to obtain the software versionAffected if The version falls outside the fixed releases: ASA < 9.8.4, ASA 9.9.0-9.9.2.49, ASA 9.10.0-9.10.1.16, FTD 6.2.1-6.2.3.11, or FTD 6.3.0-6.3.0.2
-
Confirm management interface is activeRun 'show interface' or check the device configuration for the management interface status using 'show run interface Management0/0'Affected if The management interface is enabled and reachable from an adjacent network segment
-
Check for anomalous syslog entriesReview syslog logs for messages indicating packets reaching the kernel through the management interface. Use 'show logging' or grep syslog files for kernel-related messages from the management interfaceAffected if Unexpected syslog entries appear showing Layer 2 packets bypassing detection engine filtering on the management interface
You are affected if your Cisco ASA or FTD version is within the affected ranges AND the management interface is accessible from an adjacent network segment, as the vulnerability allows crafted Ethernet frames to bypass Layer 2 filtering and reach the kernel.
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 data6.2.3.126.3.0.39.8.4
Apply the relevant Cisco security updates for ASA and FTD software. Until patches are applied, consider network segmentation to restrict physical/adjacent access to the management interface and monitor for anomalous syslog entries.
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
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 locallyCheck whether your project pulls in CVE-2019-1695 — 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-2019-1695 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