Hosted Collaboration SolutionApplication · Cisco
CVE-2013-1174
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 Tivoli Business Service Manager (TBSM) in Hosted Collaboration Mediation (HCM) in Cisco Hosted Collaboration Solution allows remote attackers to cause a denial of service (temporary service hang) by sending many TCP packets to certain ports, aka Bug ID CSCue03703.
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 Tivoli Business Service Manager (TBSM) in Hosted Collaboration Mediation (HCM) contains a denial of service vulnerability where sending a high volume of TCP packets to certain (unspecified) ports causes temporary service hang. The attack exploits insufficient handling of TCP connections leading to resource exhaustion.
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.
-
Confirm Cisco TBSM installationIdentify if Cisco Tivoli Business Service Manager (TBSM) or Hosted Collaboration Mediation (HCM) components are installed in the environment. Check for TBSM processes, services, or installed packages using system inventory tools or by reviewing installed software lists.Affected if Cisco TBSM or HCM is present in the environment
-
Verify network exposure of TBSM servicesIdentify network listeners and open ports associated with TBSM. Use netstat, ss, or network scanning tools to enumerate listening services on the host where TBSM is installed. Look for services listening on TCP ports.Affected if TBSM services are exposed on network accessible ports
-
Check for port-specific exposureReview firewall rules and network access control lists to determine which TCP ports serving TBSM are accessible from network segments. Identify any unprotected ports that could receive high-volume TCP traffic.Affected if TBSM TCP ports are accessible without adequate network filtering or rate limiting
-
Monitor for resource exhaustion symptomsCheck system resource usage (CPU, memory, network connection counts) on TBSM hosts. Review system logs, application logs, and network device logs for patterns of connection spikes, service timeouts, or hangs correlating with high TCP traffic events.Affected if Resource exhaustion or service hangs are observed under high TCP connection load
-
Review network traffic patternsAnalyze network flow data, packet captures, or intrusion detection alerts for unusually high volumes of TCP connections directed toward TBSM service ports from external or internal sources.Affected if Unusual high-volume TCP traffic toward TBSM services is detected
A user is affected if Cisco TBSM or Hosted Collaboration Mediation is installed and its TCP service ports are network-accessible without adequate rate limiting or filtering, enabling potential resource exhaustion attacks.
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-level filtering or rate limiting for traffic to affected TBSM services; contact Cisco for specific patch information and port details per Bug ID CSCue03703.
Fix this in Hosted Collaboration Solution
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1174 — 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-1174 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