# CVE-2013-6708: Information disclosure in n/a

> Remote attackers can read arbitrary files from Cisco Cloud Portal via direct requests, leading to information disclosure.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-74c7-c9pw-mwmq

## What is CVE-2013-6708?

CVE-2013-6708 is a medium-severity vulnerability in n/a, published on 10 Dec 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco Cloud Portal 9.4 allows remote attackers to read files of unspecified types via a direct request, aka Bug IDs CSCuj08426 and CSCui60889.

Weakness: CWE-264

## Which versions are affected by CVE-2013-6708?

It affects 1 product.


Products: Cisco Cloud Portal.

## How do I fix CVE-2013-6708?

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

## Is CVE-2013-6708 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-3351](https://insights.sbomify.com/CVE-2014-3351/): Information disclosure in n/a (medium 5.0)
- [CVE-2014-0694](https://insights.sbomify.com/CVE-2014-0694/): Hardcoded credentials in n/a (medium 5.0)
- [CVE-2014-3352](https://insights.sbomify.com/CVE-2014-3352/): Information disclosure in n/a (medium 4.3)
- [CVE-2014-3349](https://insights.sbomify.com/CVE-2014-3349/): File upload in n/a (medium 4.0)
- [CVE-2014-3350](https://insights.sbomify.com/CVE-2014-3350/): Open redirect in n/a (medium 4.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6708 and fix it if it is affected.

What it is: CVE-2013-6708 is a medium-severity vulnerability in n/a, published on 10 Dec 2013. 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-2013-6708 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-2013-6708/ (Markdown: https://insights.sbomify.com/CVE-2013-6708/index.md)
```

## Sources

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

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