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

> Remote attackers can obtain sensitive query string or cookie information from Cisco MediaSense due to improper protection of the client-server communication channel.

- **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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 23 Sep 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-j8f3-8cwh-jxqr

## What is CVE-2013-5502?

CVE-2013-5502 is a medium-severity vulnerability in n/a, published on 23 Sep 2013. It can be exploited over the network.

### Official description

The web interface in Cisco MediaSense does not properly protect the client-server communication channel, which allows remote attackers to obtain sensitive query string or cookie information via unspecified vectors, aka Bug ID CSCuj23344.

Weakness: CWE-264

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

It affects 1 product.


Products: Cisco Mediasense.

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

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

## Is CVE-2013-5502 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-0736](https://insights.sbomify.com/CVE-2015-0736/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2014-0671](https://insights.sbomify.com/CVE-2014-0671/): Open redirect in n/a (medium 5.8)
- [CVE-2014-0670](https://insights.sbomify.com/CVE-2014-0670/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2013-5500](https://insights.sbomify.com/CVE-2013-5500/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2013-5501](https://insights.sbomify.com/CVE-2013-5501/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-5502 is a medium-severity vulnerability in n/a, published on 23 Sep 2013. It can be exploited over the network.
Exploitation: There is no known exploitation of CVE-2013-5502 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-5502/ (Markdown: https://insights.sbomify.com/CVE-2013-5502/index.md)
```

## Sources

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

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