# CVE-2021-44746: Information disclosure in n/a

> Remote attackers with internal network access can obtain sensitive configuration information from NEC UNIVERGE IP phones and management tools.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 1 Feb 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8r5p-3w3p-m2rh

## What is CVE-2021-44746?

CVE-2021-44746 is a medium-severity vulnerability in n/a, published on 1 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

UNIVERGE DT 820 V3.2.7.0 and prior, UNIVERGE DT 830 V5.2.7.0 and prior, UNIVERGE DT 930 V2.4.0.0 and prior, IP Phone Manager V8.9.1 and prior, Data Maintenance Tool for DT900 Series V5.3.0.0 and prior, Data Maintenance Tool for DT800 Series V4.2.0.0 and prior allows a remote attacker who can access to the internal network, the configuration information may be obtained.

## Which versions are affected by CVE-2021-44746?

It affects 6 products.


Products: Nec Univerge Dt800 Data Maintenance Tool, Nec Univerge Dt820 Firmware, Nec Univerge Dt830 Firmware, Nec Univerge Dt900 Data Maintenance Tool, Nec Univerge Dt930 Firmware, Nec Univerge Ip Phone Manager.

## How do I fix CVE-2021-44746?

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

## Is CVE-2021-44746 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-44746 and fix it if it is affected.

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

## Sources

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

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