dbcve.org
Kb Ahr04d FirmwareOperating system · Kbdevice

CVE-2023-30766

CRITICAL · 9.8 CVSS v3.1 Published 2023-06-13
Fix available
A fix is available. Upgrade to 91110.1.101106.78 / 91210.1.101106.78 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 issue exists in KB-AHR series and KB-IRIP series. If this vulnerability is exploited, an arbitrary OS command may be executed on the product or the device settings may be altered. Affected products and versions are as follows: KB-AHR04D versions prior to 91110.1.101106.78, KB-AHR08D versions prior to 91210.1.101106.78, KB-AHR16D versions prior to 91310.1.101106.78, KB-IRIP04A versions prior to 95110.1.100290.78A, KB-IRIP08A versions prior to 95210.1.100290.78A, and KB-IRIP16A versions prior to 95310.1.100290.78A.

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 undocumented command interface or backdoor) in KB-AHR and KB-IRIP series devices allows unauthenticated attackers to execute arbitrary OS commands or modify device settings. The vulnerability is network-exploitable with CVSS 9.8 indicating no authentication required and complete impact on confidentiality, integrity, and availability.

MitigationApply vendor firmware updates to all affected devices: KB-AHR series to version 91110.1.101106.78 or later, KB-IRIP series to version 95110.1.100290.78A or later. If patching is delayed, isolate devices on restricted network segments and disable unnecessary interfaces.

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
Kb Ahr04d FirmwareOperating system
Affected:< 91110.1.101106.78
Kb Ahr08d FirmwareOperating system
Affected:< 91210.1.101106.78
Kb Ahr16d FirmwareOperating system
Affected:< 91310.1.101106.78
Kb Irip04a FirmwareOperating system
Affected:< 95110.1.100290.78a
Kb Irip08a FirmwareOperating system
Affected:< 95210.1.100290.78a
Kb Irip16a FirmwareOperating system
Affected:< 95310.1.100290.78a

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

CVSS:3.1/AV:N/AC:L/PR:N/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 in your network
    Access the device web interface, administrative console, or network discovery to determine if the device is a Kbdevice KB-AHR (AHR04d, AHR08d, AHR16d) or KB-IRIP (IRIP04a, IRIP08a, IRIP16a) series device. Check the device status page, management interface, or SNMP sysDescr for model identification.
    Affected if Device model matches KB-AHR or KB-IRIP series
  2. Locate firmware version information
    Navigate to the device administrative interface (typically web-based). Look for a System Info, Device Status, About, or Firmware Version page. The exact location varies by device but is usually under Administration, Settings, or System menu. Alternatively, check SNMP OID 1.3.6.1.2.1.1.1.0 if SNMP is enabled.
    Affected if Unable to retrieve firmware version information from the device
  3. Compare installed firmware version against affected ranges
    For KB-AHR devices (AHR04d, AHR08d, AHR16d): Compare your firmware version to 91110.1.101106.78. For KB-IRIP devices (IRIP04a, IRIP08a, IRIP16a): Compare your firmware version to 95110.1.100290.78A. Note that version comparison should treat earlier versions as vulnerable (less than the fixed version).
    Affected if Firmware version is lower than 91110.1.101106.78 (KB-AHR series) or 95110.1.100290.78A (KB-IRIP series)
  4. Inspect for undocumented interfaces or hidden functionality
    Review the device web interface for unfamiliar endpoints, hidden pages, or unusual command execution features. Check for URLs or parameters that may not be documented in normal user manuals. Look for debug pages, test interfaces, or diagnostic functions that should not be present in production firmware.
    Affected if Undocumented administrative interfaces, debug endpoints, or hidden command execution features are present on the device

Your environment is affected if you have any KB-AHR or KB-IRIP series devices running firmware versions below 91110.1.101106.78 (AHR series) or 95110.1.100290.78A (IRIP series).

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 91110.1.101106.78 / 91210.1.101106.78 / 91310.1.101106.78 or later
Fixed in 91110.1.101106.7891210.1.101106.7891310.1.101106.78
Interim mitigation

Apply vendor firmware updates to all affected devices: KB-AHR series to version 91110.1.101106.78 or later, KB-IRIP series to version 95110.1.100290.78A or later. If patching is delayed, isolate devices on restricted network segments and disable unnecessary interfaces.

Recommended fix Moderate confidence

KB-AHR series to firmware >= 91110.1.101106.78 (AHR04D), >= 91210.1.101106.78 (AHR08D), >= 91310.1.101106.78 (AHR16D); KB-IRIP series to firmware >= 95110.1.100290.78A (IRIP04A), >= 95210.1.100290.78A (IRIP08A), >= 95310.1.100290.78A (IRIP16A)

  1. Identify the specific KB device model (AHR04D, AHR08D, AHR16D, IRIP04A, IRIP08A, or IRIP16A) from the affected product list
  2. Check the current firmware version installed on the device
  3. Download the firmware update from the official vendor website (www.kbdevice.com) or contact KB device support for the fixed firmware version
  4. Upgrade the firmware to version 91110.1.101106.78 or later for KB-AHR04D, 91210.1.101106.78 or later for KB-AHR08D, 91310.1.101106.78 or later for KB-AHR16D, 95110.1.100290.78A or later for KB-IRIP04A, 95210.1.100290.78A or later for KB-IRIP08A, or 95310.1.100290.78A or later for KB-IRIP16A
  5. Verify the firmware upgrade was successful and the device is functioning normally

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

Fix this in Kb Ahr04d Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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