Media Origination System SuiteApplication · Cisco
CVE-2016-6377
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 · uneditedMedia Origination System Suite Software 2.6 and earlier in Cisco Virtual Media Packager (VMP) allows remote attackers to bypass authentication and make arbitrary Platform and Applications Manager (PAM) API calls via unspecified vectors, aka Bug ID CSCuz52110.
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 confidenceThis is an authentication bypass vulnerability in Cisco Virtual Media Packager (VMP) affecting version 2.6 and earlier. Attackers can bypass authentication entirely and make arbitrary calls to the Platform and Applications Manager (PAM) API, effectively gaining full administrative control over the system without credentials.
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
Media Origination System SuiteApplication
= 2.3\(1\)= 2.3\(2\)= 2.3\(6\)= 2.3\(7\)= 2.3\(8\)= 2.3_base= 2.4\(1\)= 2.4_base= 2.5\(0\)= 2.5\(1\)= 2.5_base= 2.6_baseCVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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.
-
Identify if Cisco Virtual Media Packager is installedLocate VMP installation directories or check system inventory for Cisco Media Origination System Suite software packagesAffected if VMP software is present on the system
-
Determine the installed VMP versionRun version check command or inspect version files for the Virtual Media Packager installationAffected if The installed version is 2.6 or earlier, or matches any of these: 2.3(1), 2.3(2), 2.3(6), 2.3(7), 2.3(8), 2.3_base, 2.4(1), 2.4_base, 2.5(0), 2.5(1), 2.5_base, 2.6_base
-
Verify if PAM API management interface is network-accessibleCheck firewall rules, ACLs, or network configuration to determine if the Platform and Applications Manager (PAM) API ports are exposed to untrusted networksAffected if PAM API is accessible from networks outside trusted management segments
-
Confirm authentication is enforced on VMP management endpointsAttempt an unauthenticated request to PAM API endpoints or inspect authentication configuration logs for bypass attemptsAffected if Unauthenticated requests succeed or authentication can be bypassed entirely
You are affected if Cisco Virtual Media Packager version 2.6 or earlier is installed AND the PAM API management interface is network-accessible, allowing unauthenticated administrative access.
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 vendor patch for this vulnerability. Until patched, restrict network access to the VMP management interfaces using firewall rules or ACLs to limit exposure to trusted networks only.
Fix this in Media Origination System Suite
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-6377 — 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-6377 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