Adaptive Security Appliance SoftwareOperating system · Cisco
CVE-2014-2129
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 · uneditedThe SIP inspection engine in Cisco Adaptive Security Appliance (ASA) Software 8.2 before 8.2(5.48), 8.4 before 8.4(6.5), 9.0 before 9.0(3.1), and 9.1 before 9.1(2.5) allows remote attackers to cause a denial of service (memory consumption or device reload) via crafted SIP packets, aka Bug ID CSCuh44052.
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 confidenceThe SIP inspection engine in Cisco ASA Software contains a denial of service vulnerability where crafted SIP packets can cause memory consumption or device reload. This is a network-based attack requiring no authentication.
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 SoftwareOperating system
= 8.2= 8.4= 9.0= 9.1CVSS 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
- M
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:M/Au:N/C:N/I:N/A:C
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.
-
Verify Cisco ASA device and obtain software versionAccess the ASA CLI and run 'show version' to display the installed Cisco Adaptive Security Appliance Software version and build numberAffected if The device is running Cisco ASA Software and the version falls within 8.2.x (before 8.2(5.48)), 8.4.x (before 8.4(6.5)), 9.0.x (before 9.0(3.1)), or 9.1.x (before 9.1(2.5))
-
Confirm SIP inspection is enabledRun 'show run all inspection' or 'show service-policy' in the ASA CLI to inspect the active inspection configurationAffected if SIP inspection is present in the active configuration, indicating the SIP inspection engine is loaded and processing SIP traffic
-
Check for SIP-specific class or policy mapsRun 'show run | include sip' or examine the inspection policy map configuration to identify any SIP-related inspection rulesAffected if A SIP inspection policy map is defined and applied to traffic, meaning the device is actively inspecting SIP packets
-
Verify SIP traffic is permitted through the deviceReview access control policies and run 'show conn' to identify any active SIP connections, or check if SIP traffic is allowed from untrusted external sourcesAffected if SIP traffic from untrusted networks is permitted through the ASA and SIP inspection is active on that traffic
You are affected if your Cisco ASA runs a vulnerable software version (8.2, 8.4, 9.0, or 9.1 branch before the fixed releases) AND SIP inspection is enabled and processing SIP traffic from accessible network paths.
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 dataUpgrade Cisco ASA Software to version 8.2(5.48), 8.4(6.5), 9.0(3.1), 9.1(2.5) or later. As an interim mitigation, consider disabling SIP inspection if not required, or restricting SIP traffic to trusted sources at network perimeter.
Fix this in Adaptive Security Appliance Software
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2129 — 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-2014-2129 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