dbcve.org
Adaptive Security Appliance SoftwareApplication · Cisco

CVE-2015-0742

MEDIUM · 5.0 CVSS v2.0 Published 2015-05-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
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
The Protocol Independent Multicast (PIM) application in Cisco Adaptive Security Appliance (ASA) Software 9.2(0.0), 9.2(0.104), 9.2(3.1), 9.2(3.4), 9.3(1.105), 9.3(2.100), 9.4(0.115), 100.13(0.21), 100.13(20.3), 100.13(21.9), and 100.14(1.1) does not properly implement multicast-forwarding registration, which allows remote attackers to cause a denial of service (forwarding outage) via a crafted multicast packet, aka Bug ID CSCus74398.

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

The Protocol Independent Multicast (PIM) implementation in Cisco ASA Software has improper multicast-forwarding registration handling. Remote attackers can send crafted multicast packets to trigger a forwarding outage, causing denial of service. The vulnerability affects multiple ASA software versions across 9.2.x, 9.3.x, 9.4.x, 100.13.x, and 100.14.x branches.

MitigationApply the relevant Cisco ASA software update from the advisory. If immediate patching is not feasible, implement ingress ACLs on interface(s) to filter unauthorized or unexpected PIM multicast traffic destined for the ASA.

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
Affected:= 9.2\(3.4\)= 9.4\(0.115\)= 100.13\(0.21\)= 100.13\(20.3\)= 100.13\(21.9\)= 9.2\(0.0\)= 9.2\(0.104\)= 9.2\(3.1\)= 9.3\(1.105\)= 9.3\(2.100\)= 100.14\(1.1\)

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
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

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 ASA software version
    Run 'show version' on the ASA CLI to obtain the installed software version number
    Affected if The displayed version matches any of these: 9.2(0.0), 9.2(0.104), 9.2(3.1), 9.2(3.4), 9.3(1.105), 9.3(2.100), 9.4(0.115), 100.13(0.21), 100.13(20.3), 100.13(21.9), 100.14(1.1)
  2. Verify PIM is enabled
    Run 'show running-config | include pim' or 'show ip pim interface' to check if Protocol Independent Multicast is configured
    Affected if PIM is actively enabled on one or more interfaces (the vulnerability only affects systems with PIM running)
  3. Confirm multicast routing is active
    Run 'show ip multicast' or 'show running-config | include multicast' to verify multicast routing functionality
    Affected if Multicast routing is enabled - this is required for PIM to process the malicious packets
  4. Check PIM neighbor relationships
    Run 'show ip pim neighbor' to see if PIM neighbors exist on the affected interfaces
    Affected if PIM neighbors are present and the ASA is actively participating in multicast routing

You are affected if the ASA runs an affected software version AND has PIM multicast forwarding enabled on any interface.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Cisco ASA software update from the advisory. If immediate patching is not feasible, implement ingress ACLs on interface(s) to filter unauthorized or unexpected PIM multicast traffic destined for the ASA.

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
12.0 hours of engineering $2,130
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-0742 — 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-2015-0742 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