dbcve.org
Ahb7008t Mh V2 FirmwareOperating system · Xiongmaitech

CVE-2020-22253

CRITICAL · 9.8 CVSS v3.1 Published 2022-04-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Xiongmai Technology Co devices AHB7008T-MH-V2, AHB7804R-ELS, AHB7804R-MH-V2, AHB7808R-MS-V2, AHB7808R-MS, AHB7808T-MS-V2, AHB7804R-LMS, and HI3518E_50H10L_S39 were all discovered to have port 9530 open which allows unauthenticated attackers to make arbitrary Telnet connections with the victim device.

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

Multiple Xiongmai Technology Co video surveillance devices (DVRs and cameras) have an open Telnet service on port 9530 that allows unauthenticated remote attackers to connect directly to the device. This gives attackers full shell access to the compromised device, potentially enabling lateral movement, credential harvesting, or use in botnets.

MitigationRestrict network access to port 9530 using firewall rules or network segmentation to prevent external/unauthorized access. If possible, disable the Telnet service on affected devices or apply firmware updates from the vendor.

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
Ahb7008t Mh V2 FirmwareOperating system
Affected:= 4.02.r11.7601.nat.onvifc.20170420
Ahb7804r Els FirmwareOperating system
Affected:= 4.02.r11.nat.onvifc.20160422
Ahb7804r Mh V2 FirmwareOperating system
Affected:= 4.02.r11.7601.nat.onvifc.20170424
Ahb7808r Ms V2 FirmwareOperating system
Affected:= 4.02.r11.nat.onvifc.20170327
Ahb7808r Ms FirmwareOperating system
Affected:= 4.02.r11.nat.onvifc.20170328
Ahb7808t Ms V2 FirmwareOperating system
Affected:= 4.02.r11.nat.onvifc.20161205
Ahb7804r Lms FirmwareOperating system
Affected:= 4.02.r11.nat.onvifc.20170301
Hi3518e 50h10l S39 FirmwareOperating system
Affected:= 4.02.r12.nat.onvifs.20170727_all

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 Xiongmai video surveillance devices on the network
    Scan the network for devices with vendor-specific HTTP banners, or check physical device labels and management interfaces for Xiongmaitech branding. Look for DVRs and cameras with model numbers matching the affected product list (e.g., Ahb7008t, Ahb7804r, Ahb7808r, Hi3518e).
    Affected if The device is an Xiongmai Technology Co. DVR or camera matching one of the listed model numbers.
  2. Verify the installed firmware version
    Access the device web interface or administrative console and navigate to the firmware or system information section. Compare the firmware version string to the affected versions listed in the CVE (e.g., 4.02.r11.7601.nat.onvifc.20170420).
    Affected if The device firmware version exactly matches one of the eight listed firmware versions in the CVE.
  3. Check if port 9530 is open and reachable
    Use a network port scanner (such as nmap) to scan the device IP address on port 9530: 'nmap -p 9530 <device_ip>'. Alternatively, verify firewall or network ACLs allow traffic to port 9530.
    Affected if Port 9530 is reported as open and accepting TCP connections.
  4. Confirm Telnet service is listening on port 9530
    Attempt a TCP connection to port 9530 using a tool like netcat ('nc -nv <device_ip> 9530') or verify via service enumeration that port 9530 is running a Telnet service.
    Affected if A Telnet service responds on port 9530, indicating the vulnerable service is active.

A defender is affected if they have an Xiongmai device with a firmware version matching one of the eight listed versions AND port 9530 is open with an accessible Telnet service.

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

Restrict network access to port 9530 using firewall rules or network segmentation to prevent external/unauthorized access. If possible, disable the Telnet service on affected devices or apply firmware updates from the vendor.

Fix this in Ahb7008t Mh V2 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 help mitigating

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-2020-22253 — 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-2020-22253 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