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

> Local attackers can read cleartext credentials from temporary files due to weak permissions in Cisco Prime Central for HCS.

- **Severity:** Medium 4.3 (`AV:L/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Oct 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-m5jv-hrrq-wxhc

## What is CVE-2013-3409?

CVE-2013-3409 is a medium-severity vulnerability in n/a, published on 10 Oct 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The portal in Cisco Prime Central for Hosted Collaboration Solution (HCS) places cleartext credentials in temporary files, which allows local users to obtain sensitive information by leveraging weak file permissions to read these files, aka Bug IDs CSCuh33735 and CSCuh34230.

Weakness: CWE-255

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

It affects 1 product.


Products: Cisco Prime Central for Hosted Collaboration Solution.

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

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

## Is CVE-2013-3409 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-5562](https://insights.sbomify.com/CVE-2013-5562/): Denial of service in n/a (medium 5.0)
- [CVE-2013-5564](https://insights.sbomify.com/CVE-2013-5564/): Denial of service in n/a (medium 5.0)
- [CVE-2013-3398](https://insights.sbomify.com/CVE-2013-3398/): Information disclosure in n/a (medium 5.0)
- [CVE-2013-1156](https://insights.sbomify.com/CVE-2013-1156/): Path traversal in n/a (medium 5.0)
- [CVE-2013-3375](https://insights.sbomify.com/CVE-2013-3375/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-3409 is a medium-severity vulnerability in n/a, published on 10 Oct 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-3409 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-3409/ (Markdown: https://insights.sbomify.com/CVE-2013-3409/index.md)
```

## Sources

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

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