# CVE-2016-6377: Auth bypass in n/a

> Remote attackers can bypass authentication to make arbitrary API calls in Cisco Virtual Media Packager, requiring vendor patches.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2whj-c677-r58g

## What is CVE-2016-6377?

CVE-2016-6377 is a high-severity authentication bypass vulnerability in n/a, published on 3 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Media 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2016-6377?

It affects 1 product.


Products: Cisco Media Origination System Suite.

## How do I fix CVE-2016-6377?

No fix has been published for CVE-2016-6377 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-6377 being exploited?

There is no known exploitation of CVE-2016-6377 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6377 and fix it if it is affected.

What it is: CVE-2016-6377 is a high-severity authentication bypass vulnerability in n/a, published on 3 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6377 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-6377/ (Markdown: https://insights.sbomify.com/CVE-2016-6377/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-6377
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-6377
- OSV: https://osv.dev/vulnerability/CVE-2016-6377

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-6377/
Summaries are generated and may contain mistakes; the official description above is the record.