dbcve.org
Udr Ja1604 FirmwareOperating system · Unimo

CVE-2022-44606

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
OS command injection 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 · high confidence

OS command injection vulnerability in UDR-JA1604/UDR-JA1608/UDR-JA1616 network devices allows a remote authenticated attacker to execute arbitrary OS commands on the device or alter device settings through specially crafted input in firmware versions 71x10.1.107112.43A and earlier.

MitigationUpgrade firmware to a patched version beyond 71x10.1.107112.43A that addresses the command injection vulnerability, and implement network segmentation/restrict management interface access to trusted IPs until patching is complete.

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 CLI and check the model name/system information to confirm it is a UDR-JA1604, UDR-JA1608, or UDR-JA1616
    Affected if Device is not one of these three models - the vulnerability does not apply
  2. Check firmware version
    Navigate to the device firmware/version settings in the web interface or run 'show version' command via CLI to retrieve the installed firmware version
    Affected if Firmware version is 71x10.1.107112.43A or earlier, or any version below 71x10.1.107114.43a
  3. Verify management interface exposure
    Check network configuration to determine if the device management interface (HTTP/HTTPS/SSH) is reachable from untrusted networks or the internet
    Affected if Management interface is accessible from untrusted networks without network segmentation or IP restrictions
  4. Confirm authentication status
    Review device security settings to verify whether remote authentication is enabled and configured for management access
    Affected if Remote authentication is enabled and allows access from untrusted IPs, as the vulnerability requires an authenticated attacker

You are affected if you are running a UDR-JA1604/1608/1616 device with firmware version 71x10.1.107112.43A or earlier, and the management interface is accessible to remote attackers.

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

Upgrade firmware to a patched version beyond 71x10.1.107112.43A that addresses the command injection vulnerability, and implement network segmentation/restrict management interface access to trusted IPs until patching is complete.

Recommended fix High confidence

71x10.1.107114.43a or later

  1. Check current firmware version on the UDR-JA1604/UDR-JA1608/UDR-JA1616 device
  2. Download firmware version 71x10.1.107114.43a or later from the vendor's official support site (www.unimo.co.jp)
  3. Access the device administrative interface and navigate to the firmware update section
  4. Upload and install the downloaded firmware file following the vendor's documented update procedure
  5. After reboot, verify the firmware has been updated to version 71x10.1.107114.43a or later

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
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-44606 — 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-44606 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