# CVE-2022-29855: Auth bypass in n/a

> An attacker with physical access can bypass authentication during startup to gain root privileges and execute code on Mitel SIP phones.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 11 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4f6f-x4m3-rhqj

## What is CVE-2022-29855?

CVE-2022-29855 is a medium-severity authentication bypass vulnerability in n/a, published on 11 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Mitel 6800 and 6900 Series SIP phone devices through 2022-04-27 have "undocumented functionality." A vulnerability in Mitel 6800 Series and 6900 Series SIP phones excluding 6970, versions 5.1 SP8 (5.1.0.8016) and earlier, and 6.0 (6.0.0.368) through 6.1 HF4 (6.1.0.165), could allow a unauthenticated attacker with physical access to the phone to gain root access due to insufficient access control for test functionality during system startup. A successful exploit could allow access to sensitive information and code execution.

## Which versions are affected by CVE-2022-29855?

It affects 9 products.


Products: Mitel 6865i Sip Firmware, Mitel 6867i Sip Firmware, Mitel 6869i Sip Firmware, Mitel 6873i Sip Firmware, Mitel 6905 Sip Firmware, Mitel 6910 Sip Firmware, Mitel 6920 Sip Firmware, Mitel 6930 Sip Firmware, Mitel 6940 Sip Firmware.

## How do I fix CVE-2022-29855?

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

## Is CVE-2022-29855 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29855 and fix it if it is affected.

What it is: CVE-2022-29855 is a medium-severity authentication bypass vulnerability in n/a, published on 11 May 2022. 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-2022-29855 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-2022-29855/ (Markdown: https://insights.sbomify.com/CVE-2022-29855/index.md)
```

## Sources

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

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