# CVE-2015-6304: Cross-site request forgery in n/a

> Remote attackers can hijack user authentication via CSRF in Cisco TelePresence Server, requiring user interaction to execute malicious actions.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 24 Sep 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3r3c-9579-33c4

## What is CVE-2015-6304?

CVE-2015-6304 is a medium-severity vulnerability in n/a, published on 24 Sep 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in Cisco TelePresence Server software 3.0(2.24) allows remote attackers to hijack the authentication of arbitrary users, aka Bug IDs CSCut63718, CSCut63724, and CSCut63760.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Cisco Telepresence Server Software.

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

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

## Is CVE-2015-6304 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-6284](https://insights.sbomify.com/CVE-2015-6284/): Memory corruption in n/a (high 7.8)
- [CVE-2015-0660](https://insights.sbomify.com/CVE-2015-0660/): Command injection in n/a (high 7.2)
- [CVE-2017-3815](https://insights.sbomify.com/CVE-2017-3815/): Auth bypass in Cisco TelePresence Server (medium 5.3)
- [CVE-2014-3324](https://insights.sbomify.com/CVE-2014-3324/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-6304 is a medium-severity vulnerability in n/a, published on 24 Sep 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-6304 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-6304/ (Markdown: https://insights.sbomify.com/CVE-2015-6304/index.md)
```

## Sources

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

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