# CVE-2019-18863: Weak cryptography in n/a

> Weak SRTP key implementation allows man-in-the-middle attackers to intercept sensitive call data on Mitel SIP phones.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Mar 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-68jq-f8j4-qrjp

## What is CVE-2019-18863?

CVE-2019-18863 is a medium-severity vulnerability in n/a, published on 2 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A key length vulnerability in the implementation of the SRTP 128-bit key on Mitel 6800 and 6900 SIP series phones, versions 5.1.0.2051 SP2 and earlier, could allow an attacker to launch a man-in-the-middle attack when SRTP is used in a call. A successful exploit may allow the attacker to intercept sensitive information.

Weakness: CWE-326 (Inadequate Encryption Strength)

## Which versions are affected by CVE-2019-18863?

It affects 8 products.


Products: Mitel 6863i Firmware, Mitel 6865i Firmware, Mitel 6867i Firmware, Mitel 6869i Firmware, Mitel 6873i Firmware, Mitel 6920 Firmware, Mitel 6930 Firmware, Mitel 6940 Firmware.

## How do I fix CVE-2019-18863?

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

## Is CVE-2019-18863 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-18863 and fix it if it is affected.

What it is: CVE-2019-18863 is a medium-severity vulnerability in n/a, published on 2 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-18863 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-2019-18863/ (Markdown: https://insights.sbomify.com/CVE-2019-18863/index.md)
```

## Sources

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

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