# CVE-2015-6419: Information disclosure in n/a

> Authenticated remote attackers can read arbitrary files on Cisco FireSIGHT Management Center via crafted GET requests.

- **Severity:** Medium 6.8 (`AV:N/AC:L/Au:S/C:C/I:N/A:N`)
- **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-f83p-ccx3-r342

## What is CVE-2015-6419?

CVE-2015-6419 is a medium-severity 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 FireSIGHT Management Center with software 4.10.3, 5.2.0, 5.3.0, 5.3.1, and 5.4.0 allows remote authenticated users to read arbitrary files via a crafted GET request, aka Bug ID CSCur25410.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Cisco Firesight System Software.

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

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

## Is CVE-2015-6419 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-6394](https://insights.sbomify.com/CVE-2016-6394/): Auth bypass in n/a (critical 9.1)
- [CVE-2015-6335](https://insights.sbomify.com/CVE-2015-6335/): Privilege escalation in n/a (critical 9.0)
- [CVE-2016-6417](https://insights.sbomify.com/CVE-2016-6417/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2016-1394](https://insights.sbomify.com/CVE-2016-1394/): Hardcoded credentials in n/a (high 8.6)
- [CVE-2017-6766](https://insights.sbomify.com/CVE-2017-6766/): Security feature bypass in Cisco Firepower System Software (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-6419 is a medium-severity 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-6419 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-6419/ (Markdown: https://insights.sbomify.com/CVE-2015-6419/index.md)
```

## Sources

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

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