Content Delivery System EngineHardware / appliance · Cisco
CVE-2011-1649
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 Internet Streamer application in Cisco Content Delivery System (CDS) with software 2.5.7, 2.5.8, and 2.5.9 before build 126 allows remote attackers to cause a denial of service (Web Engine crash) via a crafted URL, aka Bug IDs CSCtg67333 and CSCth25341.
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 Internet Streamer application in Cisco Content Delivery System (CDS) versions 2.5.7, 2.5.8, and 2.5.9 before build 126 contains a vulnerability where specially crafted URLs cause the Web Engine to crash, resulting in denial of service. This is a remote unauthenticated attack vector with high availability impact.
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
Content Delivery System EngineHardware / appliance
all versions
Content Delivery SystemApplication
= 2.5.7= 2.5.8= 2.5.9CVSS 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
- Complete
AV:N/AC:L/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.
-
Confirm Cisco CDS installationIdentify if Cisco Content Delivery System is deployed in your environment. Check for CDS servers or appliances on the network. Look for the product name in inventory systems or documentation.Affected if Cisco CDS is not installed in the environment, the system is not affected.
-
Verify CDS software versionAccess the CDS management interface or CLI and retrieve the software version. On the command line, this is typically shown via 'show version' or accessible through the admin web interface under System > Software Upgrade or similar.Affected if The installed version is 2.5.7, 2.5.8, or 2.5.9.
-
Check build numberLocate the build number in the CDS software information. This is usually displayed alongside the version number in the admin interface or via 'show version' output. Confirm whether the build is earlier than build 126.Affected if The build number is earlier than 126 on versions 2.5.7, 2.5.8, or 2.5.9.
-
Confirm Internet Streamer is enabledDetermine if the Internet Streamer application is configured and running on the CDS. Check the CDS management interface for enabled applications or use CLI commands to list active services.Affected if Internet Streamer is enabled and the version/build conditions are met, the system is vulnerable.
A system is affected if it runs Cisco CDS versions 2.5.7, 2.5.8, or 2.5.9 with a build number earlier than 126 and has the Internet Streamer application enabled, exposing the Web Engine to remote unauthenticated DoS 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 dataUpgrade Cisco CDS software to build 126 or later to patch the vulnerability. If immediate patching is not possible, consider restricting access to the Internet Streamer application via network segmentation or firewall rules.
Fix this in Content Delivery System Engine
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-1649 — 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-2011-1649 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