# CVE-2020-13617: Information disclosure in n/a

> Unauthenticated attackers can expose sensitive information via improper memory handling during failed login attempts on Mitel SIP phones.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** 26 Aug 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8jxm-9mpx-w435

## What is CVE-2020-13617?

CVE-2020-13617 is a high-severity vulnerability in n/a, published on 26 Aug 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Web UI component of Mitel MiVoice 6800 and 6900 series SIP Phones with firmware before 5.1.0.SP5 could allow an unauthenticated attacker to expose sensitive information due to improper memory handling during failed login attempts.

Weakness: CWE-307 (Improper Restriction of Excessive Authentication Attempts)

## Which versions are affected by CVE-2020-13617?

It affects 11 products.


Products: Mitel 6863 Firmware, Mitel 6865 Firmware, Mitel 6867 Firmware, Mitel 6869 Firmware, Mitel 6873 Firmware, Mitel 6905 Firmware, Mitel 6910 Firmware, Mitel 6920 Firmware, Mitel 6930 Firmware, Mitel 6940 Firmware, Mitel 6970 Firmware.

## How do I fix CVE-2020-13617?

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

## Is CVE-2020-13617 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-13617 and fix it if it is affected.

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

## Sources

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

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