dbcve.org
Udr Ja1604 FirmwareOperating system · Unimo

CVE-2022-44620

HIGH · 8.8 CVSS v3.1 Published 2022-12-07
Fix available
A fix is available. Upgrade to 71x10.1.107114.43a or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Improper authentication vulnerability in UDR-JA1604/UDR-JA1608/UDR-JA1616 firmware versions 71x10.1.107112.43A and earlier allows a remote authenticated attacker to execute an arbitrary OS command on the device or alter the device settings.

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 · moderate confidence

Improper authentication in Uniview UDR-JA1604/1608/1616 NVR devices (firmware 71x10.1.107112.43A and earlier) allows authenticated users to bypass intended security controls, enabling arbitrary OS command execution or unauthorized modification of device settings. This suggests a privilege escalation or authentication bypass flaw in the web interface or API.

MitigationApply vendor firmware update to patched version if available; otherwise restrict network access to management interfaces, enforce strong authentication credentials, and monitor for unauthorized commands.

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
Udr Ja1604 FirmwareOperating system
Affected:< 71x10.1.107114.43a
Udr Ja1608 FirmwareOperating system
Affected:< 71x10.1.107114.43a
Udr Ja1616 FirmwareOperating system
Affected:< 71x10.1.107114.43a

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the device web interface or check the device label/metadata to confirm the exact model number is UDR-JA1604, UDR-JA1608, or UDR-JA1616.
    Affected if Device is not one of these three Uniview NVR models.
  2. Check firmware version
    Log into the device web interface and navigate to System > System Info, or use the device's API to query the firmware version. Look for a version string like 71x10.1.107xxx.43a.
    Affected if Firmware version is 71x10.1.107112.43a or earlier, or version is less than 71x10.1.107114.43a.
  3. Verify web interface is accessible
    Confirm the device web management interface (HTTP/HTTPS on ports 80 or 443, or custom ports) is reachable on the network.
    Affected if Web interface is not accessible at all.
  4. Review user accounts and privileges
    Log into the device as an administrator and navigate to User Management or Account settings. List all configured user accounts and their privilege levels.
    Affected if Unexpected or unauthorized user accounts exist, or standard users have elevated privileges.
  5. Check for suspicious configuration changes
    Review system logs or configuration backups for any recent changes to network settings, user accounts, or scheduled tasks that were not initiated by authorized administrators.
    Affected if Configuration changes exist that were not made by known administrators.

The device is affected if it is a UDR-JA1604/1608/1616 NVR running firmware version 71x10.1.107114.43a or lower, and the web interface is accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 71x10.1.107114.43a or later
Fixed in 71x10.1.107114.43a
Interim mitigation

Apply vendor firmware update to patched version if available; otherwise restrict network access to management interfaces, enforce strong authentication credentials, and monitor for unauthorized commands.

Recommended fix High confidence

Upgrade to firmware version 71x10.1.107114.43a or later

  1. 1. Identify the current firmware version of the UDR-JA1604/UDR-JA1608/UDR-JA1616 device
  2. 2. Download the fixed firmware version 71x10.1.107114.43a from the official vendor source (www.unimo.co.jp)
  3. 3. Follow the vendor's standard firmware upgrade procedure for the UDR-JA series device
  4. 4. Verify the firmware upgrade was successful by confirming the new version is 71x10.1.107114.43a or later
  5. 5. After upgrade, verify that the improper authentication vulnerability is no longer present
Caveat Review vendor release notes for any changes to device behavior or configuration requirements in the new firmware version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Udr Ja1604 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-44620 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-44620 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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