Hosted Collaboration SolutionApplication · Cisco
CVE-2013-3381
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 · uneditedCisco Hosted Collaboration Mediation allows remote attackers to cause a denial of service (CPU consumption) via a flood of malformed UDP packets on port 162, aka Bug ID CSCug85756.
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 confidenceCisco Hosted Collaboration Mediation contains a denial of service vulnerability where remote attackers can cause excessive CPU consumption by sending a flood of malformed UDP packets to port 162 (SNMP trap port). The malformed packets trigger a processing loop that consumes server resources.
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
Hosted Collaboration SolutionApplication
all versionsCVSS 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.
-
Identify Cisco Hosted Collaboration Solution installationDetermine if any component of Cisco Hosted Collaboration Solution is deployed in your environment. Check inventory systems, consult with IT asset management, or inspect running services for Cisco HCS components.Affected if Cisco Hosted Collaboration Solution is present and has UDP port 162 accessible to untrusted networks.
-
Verify UDP port 162 exposureScan or inspect network configuration to determine if UDP port 162 (SNMP trap port) is listening and accessible from external or untrusted network segments.Affected if UDP port 162 is exposed to networks accessible by potential attackers.
-
Confirm SNMP trap reception is enabledCheck the configuration of the Cisco Hosted Collaboration Mediation component to determine if SNMP trap reception or SNMP processing is actively enabled.Affected if SNMP trap reception is enabled and processing is active on the affected system.
-
Monitor for excessive CPU consumptionObserve system resource utilization on the mediation server, particularly CPU usage patterns that may indicate a processing loop triggered by malformed packet handling.Affected if The server shows sustained high CPU usage that correlates with incoming UDP traffic on port 162.
You are affected if you run any version of Cisco Hosted Collaboration Solution with SNMP trap reception enabled and UDP port 162 exposed to untrusted networks.
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 dataImplement network-based filtering or rate-limiting for UDP traffic destined for port 162 at the network perimeter. Consider blocking or restricting untrusted sources from reaching port 162.
Fix this in Hosted Collaboration Solution
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3381 — 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-2013-3381 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