# CVE-2003-20001: Information disclosure in n/a

> Remote attackers can obtain call details and SMDR records by triggering a race condition during TELNET login on Mitel ICP VoIP devices.

- **Severity:** Medium 5.6 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Apr 2025
- **Updated:** 4 Apr 2025
- **Also known as:** GHSA-w3mx-ghvj-8vc2

## What is CVE-2003-20001?

CVE-2003-20001 is a medium-severity vulnerability in n/a, published on 1 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered on Mitel ICP VoIP 3100 devices. When a remote user attempts to log in via TELNET during the login wait time and an external call comes in, the system incorrectly divulges information about the call and any SMDR records generated by the system. The information provided includes the service type, extension number and other parameters, related to the call activity.

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

## Which versions are affected by CVE-2003-20001?


## How do I fix CVE-2003-20001?

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

## Is CVE-2003-20001 being exploited?

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

Public exploit code:

- Mitel mitel-cs018 - Call Data Information Disclosure (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-20001 and fix it if it is affected.

What it is: CVE-2003-20001 is a medium-severity vulnerability in n/a, published on 1 Apr 2025. 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-2003-20001 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-2003-20001/ (Markdown: https://insights.sbomify.com/CVE-2003-20001/index.md)
```

## Sources

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

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