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

> Attackers can perform man-in-the-middle attacks to steal hashed passwords from Vocera handsets using PEAP due to lack of server certificate validation.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** 3 Mar 2008
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-74pp-9w49-8mr2

## What is CVE-2008-1114?

CVE-2008-1114 is a medium-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

Vocera Communications wireless handsets, when using Protected Extensible Authentication Protocol (PEAP), do not validate server certificates, which allows remote wireless access points to steal hashed passwords and conduct man-in-the-middle (MITM) attacks.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Vocera Wireless Handset.

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

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

## Is CVE-2008-1114 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2008-1114 is a medium-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-1114 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-1114/ (Markdown: https://insights.sbomify.com/CVE-2008-1114/index.md)
```

## Sources

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

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