# CVE-2008-1113: Security feature bypass in n/a

> Remote attackers can steal hashed passwords and conduct MITM attacks on Cisco IP Phones using PEAP due to missing certificate validation.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/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:** 3 Mar 2008
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-mx3g-c2pm-2gmw

## What is CVE-2008-1113?

CVE-2008-1113 is a high-severity vulnerability in n/a, published on 3 Mar 2008. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cisco Unified Wireless IP Phone 7921, when using Protected Extensible Authentication Protocol (PEAP), does not validate server certificates, which allows remote wireless access points to steal hashed passwords and conduct man-in-the-middle (MITM) attacks.

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

## Which versions are affected by CVE-2008-1113?

It affects 1 product.


Products: Vocera Communications Vocera Communications Badge.

## How do I fix CVE-2008-1113?

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

## Is CVE-2008-1113 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1113 and fix it if it is affected.

What it is: CVE-2008-1113 is a high-severity vulnerability in n/a, published on 3 Mar 2008. 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-2008-1113 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-2008-1113/ (Markdown: https://insights.sbomify.com/CVE-2008-1113/index.md)
```

## Sources

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

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