CVE-2011-0391
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 TelePresence Recording Server devices with software 1.6.x allow remote attackers to cause a denial of service (thread consumption and device outage) via a malformed request, related to an "ad hoc recording" issue, aka Bug ID CSCtf97205.
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 TelePresence Recording Server devices running software version 1.6.x are vulnerable to a denial of service condition. Remote attackers can send malformed requests related to the 'ad hoc recording' feature, causing excessive thread consumption that leads to complete device outage.
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= 1.6.1= 1.6.2= 1.6.3all 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
- 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.
-
Identify the device modelAccess the device's web interface or CLI and locate the product name/model information. It should be a Cisco TelePresence Recording Server.Affected if The device is a Cisco TelePresence Recording Server
-
Check the software versionIn the device's web interface, navigate to the System or Administration section to view the software version. Alternatively, use the CLI command 'show version' or 'system version' if available.Affected if The installed version is 1.6.1, 1.6.2, or 1.6.3, or if the device is any version of Cisco TelePresence Recording Server (per the 'all versions' notation)
-
Verify ad hoc recording feature statusIn the device's web interface, navigate to the Recording or Configuration settings and check whether the 'ad hoc recording' feature is enabled. This is the vulnerable component.Affected if The ad hoc recording feature is currently enabled on the device
-
Assess network exposureDetermine if the device's management interface is accessible from untrusted networks. Check firewall rules, ACLs, or VPN configurations protecting the device.Affected if The device management interface is reachable from outside trusted administrative networks
A user is affected if they have a Cisco TelePresence Recording Server with ad hoc recording enabled and the device is network-accessible to potential attackers, particularly on versions 1.6.1 through 1.6.3.
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 Cisco patch for bug ID CSCtf97205 (upgrade to a patched software version). If patching is immediately unavailable, restrict network access to the recording server to trusted administrative interfaces to reduce attack surface.
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0391 — 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-0391 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