Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2022-45460: Unauthenticated HTTP URI buffer overflow in Xiongmai NVR devices

Published Mar 28, 2023 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS5.7%93rd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Xiongmaitech
IdentifiersCVE-2022-45460CWE-121

CVE-2022-45460 is a stack-based buffer overflow in HTTP request URI parsing on multiple Xiongmai NVR devices, including MBD6304T firmware V4.02.R11.00000117.10001.131900.00000 and NBD6808T-PL firmware V4.02.R11.C7431119.12001.130000.00000. A remote, unauthenticated attacker can trigger the overflow by sending a crafted HTTP request with an excessively long URI passed to a sprintf call. Exploitation can execute arbitrary code or crash the web server, causing a system reboot. The vulnerability is distinct from CVE-2018-10088, but may overlap CVE-2017-16725.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation permits unauthenticated remote execution of arbitrary code on an affected device. Exploitation can also crash the web server and trigger a system reboot, disrupting device availability. The execution privilege level and specific confidentiality effects are not established.

Mitigation

If you can’t patch tonight, do this now.

Reduce unnecessary network exposure of affected devices and restrict access to their HTTP services using network security controls. Isolate infected devices and check for additional compromised devices. These containment measures do not correct the underlying buffer overflow.

Remediation

Patch, then assume compromise.

Upgrade affected Xiongmai device firmware to a vendor-fixed release if one is available for the specific OEM/rebrand and hardware revision. Because Xiongmai devices are frequently rebranded, remediation should be validated against the exact model and firmware lineage rather than brand name alone. If no fixed firmware is available, replace the device with a supported model. After patching or replacement, verify that the embedded HTTP service no longer accepts malformed long URIs that trigger instability or overflow conditions.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
XiongmaitechMbd6304t Firmwareoperating_system
XiongmaitechNbd6808t-Pl Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2022-45460 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2022-45460 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2022-45460?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2022-45460, the earliest disclosed Jan 30, 2025.
Is there a patch for CVE-2022-45460?
Upgrade affected Xiongmai device firmware to a vendor-fixed release if one is available for the specific OEM/rebrand and hardware revision. Because Xiongmai devices are frequently rebranded, remediation should be validated against the exact model and firmware lineage rather than brand name alone.
What products are affected by CVE-2022-45460?
Xiongmaitech Mbd6304t Firmware and Xiongmaitech Nbd6808t-Pl Firmware.
How severe is CVE-2022-45460?
CVE-2022-45460 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 5.7% (93rd percentile) as of Oct 16, 2026.
Activity feed

Recent activity

6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+1 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware2Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.