Kb Ahr04d FirmwareOperating system · Kbdevice

CVE-2023-30764

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
OS command injection vulnerability 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

OS command injection vulnerability in KB-AHR and KB-IRIP series devices allows remote attackers to execute arbitrary OS commands or alter device settings by injecting malicious commands through unsanitized input parameters in the web interface or API.

MitigationUpdate affected devices to the specified fixed versions (KB-AHR04D: 91110.1.101106.78, KB-AHR08D: 91210.1.101106.78, KB-AHR16D: 91310.1.101106.78, KB-IRIP04A: 95110.1.100290.78A, KB-IRIP08A: 95210.1.100290.78A, KB-IRIP16A: 95310.1.100290.78A) or apply compensating controls such as network segmentation and restricting management interface access.

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
    Check device label, web interface system info page, or SSH banner for model name (KB-AHR04D, KB-AHR08D, KB-AHR16D, KB-IRIP04A, KB-IRIP08A, or KB-IRIP16A)
    Affected if Device is one of the KB-AHR or KB-IRIP series models listed in the CVE
  2. Check firmware version
    Access device web interface or CLI and navigate to system settings, firmware info, or version page; alternatively, check via SSH with 'show version' or similar command
    Affected if Firmware version is lower than 91110.1.101106.78 for AHR04D, 91210.1.101106.78 for AHR08D, 91310.1.101106.78 for AHR16D, 95110.1.100290.78A for IRIP04A, 95210.1.100290.78A for IRIP08A, or 95310.1.100290.78A for IRIP16A
  3. Verify web interface or API is accessible
    Attempt to access the device web interface via HTTP/HTTPS or check if API endpoints respond to requests
    Affected if Web interface or API is exposed and reachable on the network
  4. Check for unauthorized access indicators
    Review device logs, authentication logs, or network traffic for unexpected commands, unusual API calls, or unauthorized configuration changes
    Affected if Logs show commands or configuration changes not initiated by legitimate administrators

Device is affected if it is a KB-AHR or KB-IRIP model running firmware version below the fixed thresholds and the web interface/API 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 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

Update affected devices to the specified fixed versions (KB-AHR04D: 91110.1.101106.78, KB-AHR08D: 91210.1.101106.78, KB-AHR16D: 91310.1.101106.78, KB-IRIP04A: 95110.1.100290.78A, KB-IRIP08A: 95210.1.100290.78A, KB-IRIP16A: 95310.1.100290.78A) or apply compensating controls such as network segmentation and restricting management interface access.

Recommended fix High confidence

Firmware 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; 95310.1.100290.78A or later for KB-IRIP16A

  1. 1. Identify the exact model number of the KB device (AHR04D, AHR08D, AHR16D, IRIP04A, IRIP08A, or IRIP16A)
  2. 2. Check the current firmware version of the device through its administrative interface or system settings
  3. 3. Navigate to the official KB device support website (www.kbdevice.com) or contact KB support to obtain the fixed firmware version
  4. 4. Download the appropriate firmware update: 91110.1.101106.78 or later for AHR04D, 91210.1.101106.78 or later for AHR08D, 91310.1.101106.78 or later for AHR16D, 95110.1.100290.78A or later for IRIP04A, 95210.1.100290.78A or later for IRIP08A, 95310.1.100290.78A or later for IRIP16A
  5. 5. Review the firmware upgrade instructions provided by KB device
  6. 6. Backup current device configuration if possible
  7. 7. Apply the firmware update following the manufacturer's recommended procedure
  8. 8. Verify the firmware version has been successfully updated after the upgrade process
Caveat Review KB device release notes for any configuration or feature changes between versions; firmware upgrades may require device reconfiguration

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

Fix this in Kb Ahr04d Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-30764 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