dbcve.org
Udr Ja1604 FirmwareOperating system · Unimo

CVE-2022-43464

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
Hidden functionality 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

Hidden functionality (likely a backdoor) in UDR-JA1604/1608/1616 devices allows remote authenticated attackers to execute arbitrary OS commands or alter device settings via firmware versions 71x10.1.107112.43A and earlier.

MitigationUpgrade firmware to a version newer than 71x10.1.107112.43A; if no patch available, disable remote management or restrict access to trusted IP addresses.

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 the device model
    Access the device web interface or console and locate the model number displayed in the system information or status page. Alternatively, check the device label or packaging for UDR-JA1604, UDR-JA1608, or UDR-JA1616.
    Affected if The device is an Unimo UDR-JA1604, UDR-JA1608, or UDR-JA1616 model.
  2. Locate firmware version information
    In the device web interface, navigate to the System, Status, or About section. Look for a field labeled Firmware Version, Software Version, or similar. If using CLI, use commands such as 'show version' or 'system info' if available.
    Affected if Unable to retrieve firmware version information from the device.
  3. Compare installed version to affected range
    Take the firmware version found in the previous step and compare it numerically to 71x10.1.107114.43a. Note that versions earlier than this (such as 71x10.1.107112.43A) are affected.
    Affected if The installed firmware version is less than 71x10.1.107114.43a.
  4. Verify remote management is accessible
    Check if the device admin interface is reachable over the network from an external location. Look for settings related to Remote Management, Remote Access, or Web UI accessibility in the network or security configuration section.
    Affected if Remote management or admin web interface is enabled and accessible from untrusted networks.

The device is affected if it is a UDR-JA1604, 1608, or 1616 running firmware version earlier than 71x10.1.107114.43a and has remote management accessible.

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 version newer than 71x10.1.107112.43A; if no patch available, disable remote management or restrict access to trusted IP addresses.

Recommended fix Moderate confidence

71x10.1.107114.43a or later

  1. 1. Identify the current firmware version of the UDR-JA1604, UDR-JA1608, or UDR-JA1616 device
  2. 2. If the firmware version is 71x10.1.107112.43A or earlier, the device is vulnerable
  3. 3. Obtain the fixed firmware version 71x10.1.107114.43a or later from the official vendor (Unimo Co., Ltd.)
  4. 4. Consult the vendor's official firmware upgrade documentation for detailed instructions
  5. 5. Apply the firmware update following the vendor's recommended procedure
  6. 6. After upgrade, verify the device is running firmware 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
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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