dbcve.org
Kb Ahr04d FirmwareOperating system · Kbdevice

CVE-2023-30762

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
Improper authentication 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

This is an authentication bypass vulnerability in KB-AHR and KB-IRIP series network devices (DVRs/NVRs likely). The improper authentication flaw allows unauthenticated attackers to execute arbitrary operating system commands on the device or modify device settings. With a CVSS 9.8 rating, the vulnerability is exploitable remotely without any credentials.

MitigationUpgrade affected devices to the specified fixed firmware versions (91110.1.101106.78 or later for KB-AHR series, 95110.1.100290.78A or later for KB-IRIP series). If immediate patching is not possible, isolate these devices behind a firewall or in a restricted network segment to limit exposure.

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
    Locate the device model label on the physical device chassis or check the device information page via the web interface or administrative console
    Affected if The device is a KB-AHR04d, KB-AHR08d, KB-AHR16d, KB-IRIP04a, KB-IRIP08a, or KB-IRIP16a model
  2. Determine firmware version
    Access the device firmware or system information page through the web interface, administrative panel, or device diagnostics. Compare the installed firmware version against the affected version ranges provided
    Affected if For KB-AHR series: firmware version is below 91110.1.101106.78 (04d), 91210.1.101106.78 (08d), or 91310.1.101106.78 (16d). For KB-IRIP series: firmware version is below 95110.1.100290.78a (04a), 95210.1.100290.78a (08a), or 95310.1.100290.78a (16a)
  3. Verify network exposure
    Check whether the device management interface is accessible from untrusted networks or the public internet via firewall rules, port scans, or network segmentation reviews
    Affected if The device administrative interface is directly exposed to the internet or accessible from untrusted network segments without authentication barriers

A user is affected if they have a KB-AHR or KB-IRIP series device running firmware below the specified version thresholds AND the device is network-accessible to potential 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 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

Upgrade affected devices to the specified fixed firmware versions (91110.1.101106.78 or later for KB-AHR series, 95110.1.100290.78A or later for KB-IRIP series). If immediate patching is not possible, isolate these devices behind a firewall or in a restricted network segment to limit exposure.

Recommended fix High confidence

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

  1. 1. Identify the specific KB device model (AHR04D, AHR08D, AHR16D, IRIP04A, IRIP08A, or IRIP16A)
  2. 2. Check the current firmware version of the device
  3. 3. Obtain the fixed firmware version from the vendor's official support page at www.kbdevice.com
  4. 4. Follow the vendor's standard firmware update procedure to upgrade to the fixed version
  5. 5. Verify the firmware upgrade was successful by checking the new firmware version
  6. 6. Confirm the vulnerability is remediated by verifying proper authentication is now required

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

Fix this in Kb Ahr04d Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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