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

> Remote attackers can sniff network traffic to obtain sensitive information from Cisco Unified IP 9900 phones.

- **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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rrm6-62p2-x977

## What is CVE-2015-0602?

CVE-2015-0602 is a medium-severity vulnerability in n/a, published on 7 Feb 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The mobility extension on Cisco Unified IP 9900 phones with firmware 9.4(.1) and earlier allows remote attackers to obtain sensitive information by sniffing the network, aka Bug ID CSCuq12117.

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

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

It affects 1 product.


Products: Cisco Unified Ip Phones 9900 Series Firmware.

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

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

## Is CVE-2015-0602 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-4226](https://insights.sbomify.com/CVE-2015-4226/): Denial of service in n/a (high 7.1)
- [CVE-2015-0600](https://insights.sbomify.com/CVE-2015-0600/): Denial of service in n/a (medium 5.0)
- [CVE-2015-0603](https://insights.sbomify.com/CVE-2015-0603/): Misconfiguration in n/a (medium 4.6)

## Fix prompt for AI coding agents

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

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

## Sources

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

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