CVE-2018-15454
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 Session Initiation Protocol (SIP) inspection engine of Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause an affected device to reload or trigger high CPU, resulting in a denial of service (DoS) condition. The vulnerability is due to improper handling of SIP traffic. An attacker could exploit this vulnerability by sending SIP requests designed to specifically trigger this issue at a high rate across an affected device. Software updates that address this vulnerability are not yet available.
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 SIP inspection engine of Cisco ASA and FTD software allows an unauthenticated remote attacker to cause device reload or high CPU by sending specially crafted SIP requests at high rates, 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.4, < 9.4.4.27>= 9.6, < 9.6.4.18>= 9.8, < 9.8.3.16>= 9.9, < 9.9.2.32>= 9.10, < 9.10.1.2>= 6.1.0, < 6.1.0.7>= 6.2.0, < 6.2.0.6>= 6.2.2, < 6.2.2.4>= 6.2.3, < 6.2.3.7CVSS 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
- Changed
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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 ASA software versionLog into the ASA CLI and run 'show version' to display the installed software version. Note the full version number including the maintenance release.Affected if The displayed version falls within any of these ranges: 9.4 to 9.4.4.26, 9.6 to 9.6.4.17, 9.8 to 9.8.3.15, 9.9 to 9.9.2.31, or 9.10 to 9.10.1.1.
-
Identify the Cisco FTD software versionLog into the FTD device and run 'show version' or check the management interface to display the installed software version.Affected if The displayed version falls within any of these ranges: 6.1.0 to 6.1.0.6, 6.2.0 to 6.2.0.5, 6.2.2 to 6.2.2.3, or 6.2.3 to 6.2.3.6.
-
Determine if SIP inspection is enabledRun 'show service-policy' on the ASA or FTD CLI to list active inspection policies. Look for 'sip' in the inspection configuration. Alternatively, check the configuration with 'show run | include sip' to see if SIP inspection is configured.Affected if SIP inspection is explicitly configured and active on one or more interfaces.
-
Verify network exposure to SIP trafficReview the interface configuration to determine whether SIP traffic from untrusted external sources can reach the device. Check ACLs and interface security levels to assess if the device is directly exposed to the internet or untrusted networks on SIP ports (typically UDP/TCP 5060).Affected if The device accepts SIP traffic from untrusted or internet-facing interfaces without adequate rate-limiting or source restrictions.
The device is affected if it runs a vulnerable ASA or FTD version AND has SIP inspection enabled AND is exposed to untrusted SIP traffic, as the attacker only needs to send crafted SIP requests at high rates to trigger the DoS condition.
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.1.0.76.2.0.66.2.2.4
Apply Cisco software updates when available. As an interim measure, rate-limit SIP traffic or restrict SIP traffic to trusted sources at network boundaries to reduce exposure.
- Consultation3.0 h
- Implementation3.0 h
- Testing4.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,360.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15454 — 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-2018-15454 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