Videoscape Session Resource ManagerApplication · Cisco
CVE-2016-1467
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 Videoscape Session Resource Manager (VSRM) allows remote attackers to cause a denial of service (device restart) by sending a traffic flood to upstream devices, aka Bug ID CSCva01813.
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 Videoscape Session Resource Manager (VSRM) contains a denial of service vulnerability where the device can be forced to restart when subjected to a traffic flood directed at upstream devices. The vulnerability allows remote attackers to send malicious traffic that overwhelms the system and causes an uncontrolled restart.
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
Videoscape Session Resource ManagerApplication
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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 VSRM presenceIdentify whether Cisco Videoscape Session Resource Manager is deployed in your environment by reviewing installed software, device inventory, or running processes on applicable systemsAffected if VSRM is present and running in the environment
-
Check VSRM versionLocate and record the installed version of Cisco Videoscape Session Resource Manager using the product's CLI, web interface, or system documentationAffected if Any version of VSRM is found (all versions are affected)
-
Assess network exposureReview network configuration to determine if VSRM is directly accessible from untrusted or external networks, noting any firewall rules, ACLs, or isolation between VSRM and upstream traffic sourcesAffected if VSRM is exposed to untrusted network segments without adequate filtering
-
Review for restart eventsCheck system logs, crash dumps, or management interfaces for evidence of unexpected or unexplained device restarts that correlate with periods of high trafficAffected if Unexpected restarts are observed without documented cause
-
Evaluate upstream filteringInspect network devices and segmentation between external sources and VSRM to determine whether traffic rate limiting, DDoS protection, or filtering is configured upstreamAffected if No upstream traffic filtering or rate limiting is present between untrusted networks and VSRM
A user is affected if Cisco VSRM is deployed, exposed to untrusted traffic, and lacks upstream traffic filtering or rate limiting protections.
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 traffic rate limiting and filtering on network segments upstream from VSRM to block or throttle excessive traffic. Consider network segmentation and DDoS protection mechanisms to prevent traffic floods from reaching VSRM devices.
Fix this in Videoscape Session Resource Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1467 — 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-2016-1467 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