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

> Authenticated remote attackers can enumerate existing files in Cisco WebEx Meeting Center by analyzing error message differences during file access attempts.

- **Severity:** Medium 4.0 (`AV:N/AC:L/Au:S/C:P/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:** 31 Jul 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-5w5x-ffjj-2495

## What is CVE-2013-3425?

CVE-2013-3425 is a medium-severity vulnerability in n/a, published on 31 Jul 2013. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Meeting Center component in Cisco WebEx 11 generates different error messages for invalid file-access attempts depending on whether a file exists, which allows remote authenticated users to enumerate files via a series of SPI calls, aka Bug ID CSCuc35965.

Weakness: CWE-264

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

It affects 1 product.


Products: Cisco Webex.

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

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

## Is CVE-2013-3425 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-2875](https://insights.sbomify.com/CVE-2009-2875/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-2876](https://insights.sbomify.com/CVE-2009-2876/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-2877](https://insights.sbomify.com/CVE-2009-2877/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-2878](https://insights.sbomify.com/CVE-2009-2878/): Memory corruption in n/a (critical 9.3)
- [CVE-2009-2879](https://insights.sbomify.com/CVE-2009-2879/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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