# CVE-2015-6417: Missing authorization in n/a

> Authenticated users can bypass RBAC to read or modify database entries in Cisco VDS-SM via GUI or HTTP requests.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-52gj-mvxw-vcvp

## What is CVE-2015-6417?

CVE-2015-6417 is a medium-severity missing authorization vulnerability in n/a, published on 12 Dec 2015. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Cisco Videoscape Distribution Suite Service Manager (VDS-SM) 3.4.0 and earlier does not always use RBAC for backend database access, which allows remote authenticated users to read or write to database entries via (1) the GUI or (2) a crafted HTTP request, aka Bug ID CSCuv87025.

Weakness: CWE-264

## Which versions are affected by CVE-2015-6417?

It affects 1 product.


Products: Cisco Videoscape Distribution Suite Service Manager.

## How do I fix CVE-2015-6417?

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

## Is CVE-2015-6417 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-6418](https://insights.sbomify.com/CVE-2016-6418/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2015-6364](https://insights.sbomify.com/CVE-2015-6364/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-6417 and fix it if it is affected.

What it is: CVE-2015-6417 is a medium-severity missing authorization vulnerability in n/a, published on 12 Dec 2015. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-6417 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-2015-6417/ (Markdown: https://insights.sbomify.com/CVE-2015-6417/index.md)
```

## Sources

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

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