CVE-2021-44746
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUNIVERGE 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is an information disclosure vulnerability in NEC's UNIVERGE IP phone devices (DT820, DT830, DT930) and associated management tools (IP Phone Manager, Data Maintenance Tools). A remote attacker with access to the internal network can obtain configuration information from affected devices.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 5.2.7.0<= 3.2.7.0<= 2.4.0.0<= 5.3.0.0<= 4.2.0.0<= 8.9.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify deployed NEC UNIVERGE IP phone modelsInventory your network for NEC UNIVERGE DT820, DT830, or DT930 devices. Check device labels, DHCP reservations, or network scan results for these model numbers.Affected if Any DT820, DT830, or DT930 phones are found on the network
-
Check DT830 firmware versionAccess the DT830 phone admin interface or check via management software. Navigate to Status or System Information section to view the firmware version.Affected if Firmware version is 5.2.7.0 or lower
-
Check DT820 firmware versionAccess the DT820 phone admin interface or check via management software. Navigate to Status or System Information section to view the firmware version.Affected if Firmware version is 3.2.7.0 or lower
-
Check DT930 firmware versionAccess the DT930 phone admin interface or check via management software. Navigate to Status or System Information section to view the firmware version.Affected if Firmware version is 2.4.0.0 or lower
-
Check Data Maintenance Tool installationsReview installed programs on management workstations for Nec Univerge Dt900 Data Maintenance Tool or Dt800 Data Maintenance Tool. Verify the installed version in the application properties or About section.Affected if Data Maintenance Tool version is 5.3.0.0 or lower (Dt900) or 4.2.0.0 or lower (Dt800)
-
Check IP Phone Manager installationReview installed programs on management workstations for Nec Univerge Ip Phone Manager. Verify the installed version in the application properties or About section.Affected if IP Phone Manager version is 8.9.1 or lower
You are affected if any NEC UNIVERGE DT820/DT830/DT930 phones, Data Maintenance Tools, or IP Phone Manager with versions at or below the specified thresholds are deployed and network-accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict network access to internal networks only, implement network segmentation for IP phone infrastructure, and apply vendor patches to update to versions beyond the stated thresholds.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-44746 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-44746 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data