Ds D5b86rb\/b FirmwareOperating system · Hikvision

CVE-2023-33806

HIGH · 7.8 CVSS v3.1 Published 2024-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
Insecure default configurations in Hikvision Interactive Tablet DS-D5B86RB/B V2.3.0 build220119, allows attackers to execute arbitrary commands.

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 · moderate confidence

Insecure default configurations in Hikvision Interactive Tablet DS-D5B86RB/B firmware V2.3.0 build220119 allow remote attackers to execute arbitrary commands, likely through exposed management interfaces or services with weak/default credentials.

MitigationUpdate to vendor-provided patched firmware if available; otherwise, network-segment the device, disable unused services, and change any default credentials.

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
Ds D5b86rb\/b FirmwareOperating system
Affected:= 2.3.0

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

CVSS:3.1/AV:L/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 and firmware version
    Access the device's system settings or web interface and navigate to 'About' or 'System Info' to find the exact model number (DS-D5B86RB/B) and firmware version. Alternatively, check the Hikvision device management software or scan the network for this specific model.
    Affected if The device is a Hikvision DS-D5B86RB/B tablet running firmware version 2.3.0 (build 220119)
  2. Check for exposed management web interface
    Attempt to access the device's web interface by entering its IP address in a web browser. Look for the Hikvision login page on common ports such as 80, 443, 8080. Use a network scan tool (such as nmap) to check for open HTTP/HTTPS ports on the device.
    Affected if The device's management web interface is accessible from the network (especially untrusted networks)
  3. Verify credential status
    Attempt to log into the device using known default credentials for Hikvision devices. Common default credentials include admin/admin, admin/12345, or admin/hikvision. Check if login succeeds with these or other well-known default username/password combinations.
    Affected if Default credentials have not been changed and allow access to the device management interface

You are affected if you have a Hikvision DS-D5B86RB/B tablet running firmware V2.3.0 with exposed management interfaces that still use default credentials.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to vendor-provided patched firmware if available; otherwise, network-segment the device, disable unused services, and change any default credentials.

Fix this in Ds D5b86rb\/b Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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