Wide Area Application ServicesApplication · Cisco
CVE-2015-0730
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 SMB module in Cisco Wide Area Application Services (WAAS) 6.0(1) allows remote attackers to cause a denial of service (module reload) via an invalid field in a Negotiate Protocol request, aka Bug ID CSCuo75645.
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 confidenceThe SMB module in Cisco WAAS 6.0(1) contains a denial of service vulnerability where an attacker sending a malformed SMB Negotiate Protocol request with an invalid field can trigger a module reload. The vulnerability exists in the parsing logic of the SMB protocol handler, which fails to properly validate input fields before processing, causing the module to crash and reload.
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
Wide Area Application ServicesApplication
= 6.0\(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 checksWork through these to decide whether this CVE applies to you.
-
Check WAAS software versionExecute 'show version' or 'show waas version' command on the WAAS device to identify the installed software version.Affected if Version displayed is exactly 6.0(1)
-
Confirm SMB module is activeExecute 'show running-config' or 'show service smb' to verify the SMB optimization service is enabled on the device.Affected if SMB service is configured and active in the WAAS configuration
-
Check SMB traffic processing statusExecute 'show statistics smb' or 'show ip smb sessions' to confirm the device is processing SMB traffic.Affected if SMB sessions or statistics are being recorded, indicating active SMB traffic handling
-
Inspect SMB negotiation loggingReview system logs or debug output for SMB Negotiate Protocol request handling. Look for any logged parsing errors or异常 in the SMB protocol handler.Affected if Device logs show SMB negotiation processing is occurring without errors, as the vulnerability triggers on malformed requests
You are affected if your WAAS version is exactly 6.0(1) and the SMB optimization module is enabled and actively processing SMB traffic.
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 dataApply the appropriate Cisco patch for Bug ID CSCuo75645 to address the SMB parsing vulnerability in WAAS. If no patch is available, consider network-level filtering to restrict SMB traffic from untrusted sources.
Fix this in Wide Area Application Services
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0730 — 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-2015-0730 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