dbcve.org
Adaptive Security ApplianceApplication · Cisco

CVE-2019-12678

HIGH · 7.5 CVSS v3.1 Published 2019-10-02
Fix available
A fix is available. Upgrade to 6.2.3.15 / 6.3.0.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Session Initiation Protocol (SIP) inspection module of Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. The vulnerability is due to improper parsing of SIP messages. An attacker could exploit this vulnerability by sending a malicious SIP packet through an affected device. A successful exploit could allow the attacker to trigger an integer underflow, causing the software to try to read unmapped memory and resulting in a crash.

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 confidence

A vulnerability in the SIP inspection module of Cisco ASA and FTD software allows an unauthenticated remote attacker to cause device crash via integer underflow when parsing malicious SIP packets. The flaw causes the software to attempt reading unmapped memory, resulting in denial of service.

MitigationApply the Cisco security update/patch for ASA and FTD that addresses this SIP inspection vulnerability. Disable SIP inspection if not required, or implement rate limiting on SIP traffic as a temporary workaround until patching is feasible.

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 ApplianceApplication
Affected:< 9.4.4.37
Adaptive Security Appliance SoftwareOperating system
Affected:>= 9.5, < 9.6.4.34>= 9.7, < 9.8.4.7>= 9.9, < 9.9.2.56>= 9.10, < 9.10.1.27>= 9.12, < 9.12.2.1
Secure Firewall Threat DefenseApplication
Affected:< 6.2.3.15>= 6.3.0, < 6.3.0.4>= 6.4.0, < 6.4.0.4

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
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 checks

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

  1. Identify the Cisco device type and software version
    Run the command 'show version' on the device CLI to obtain the exact ASA or FTD software version number
    Affected if The displayed version falls within any of the affected ranges: ASA < 9.4.4.37; ASA 9.5 to < 9.6.4.34; ASA 9.7 to < 9.8.4.7; ASA 9.9 to < 9.9.2.56; ASA 9.10 to < 9.10.1.27; ASA 9.12 to < 9.12.2.1; FTD < 6.2.3.15; FTD 6.3.0 to < 6.3.0.4; or FTD 6.4.0 to < 6.4.0.4
  2. Verify if SIP inspection is enabled
    Run 'show service-policy | include sip' or 'show running-config | include sip' to check whether SIP inspection is configured on any interface
    Affected if SIP inspection is enabled and the device version is in the affected ranges listed above
  3. Check for SIP-related policy maps
    Run 'show running-config policy-map | include -i sip' or examine the configuration for any policy-map that references 'sip' inspection
    Affected if A SIP inspection policy map exists and the device version is vulnerable
  4. Confirm SIP traffic is permitted through the device
    Review access control lists or security policies to verify that UDP/TCP port 5060 (SIP) traffic is allowed through the device
    Affected if SIP traffic is permitted and the device is running a vulnerable version with SIP inspection active

The device is affected if it runs a vulnerable ASA or FTD version AND has SIP inspection enabled, allowing SIP traffic to reach the device.

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.

From vendor data
Upgrade available Upgrade to 6.2.3.15 / 6.3.0.4 / 6.4.0.4 or later
Fixed in 6.2.3.156.3.0.46.4.0.4
Interim mitigation

Apply the Cisco security update/patch for ASA and FTD that addresses this SIP inspection vulnerability. Disable SIP inspection if not required, or implement rate limiting on SIP traffic as a temporary workaround until patching is feasible.

Fix this in Adaptive Security Appliance Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2019-12678 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