CVE-2023-30466
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 · uneditedThis vulnerability exists in Milesight 4K/H.265 Series NVR models (MS-Nxxxx-xxG, MS-Nxxxx-xxE, MS-Nxxxx-xxT, MS-Nxxxx-xxH and MS-Nxxxx-xxC), due to a weak password reset mechanism at the Milesight NVR web-based management interface. A remote attacker could exploit this vulnerability by sending a specially crafted http requests on the targeted device. Successful exploitation of this vulnerability could allow remote attacker to account takeover on the targeted 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 confidenceA weak password reset mechanism in the Milesight NVR web-based management interface allows remote attackers to craft malicious HTTP requests that can take over administrator accounts. This affects multiple series (MS-Nxxxx-xxG, xxE, xxT, xxH, xxC) of 4K/H.265 NVR devices.
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< 73.9.0.18-r2< 73.9.0.18-r2< 73.9.0.18-r2< 73.9.0.18-r2< 75.9.0.18-r2< 75.9.0.18-r2< 71.9.0.18-r2< 71.9.0.18-r2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Milesight NVR device modelAccess the device's web interface or check the device label/metadata to confirm it is a Milesight NVR from the MS-Nxxxx series (such as N5008, N1008, N1004, N5016, N7016, N7032)Affected if The device is a Milesight NVR from the listed series (MS-Nxxxx-xxG, xxE, xxT, xxH, xxC)
-
Determine the installed firmware versionLog into the NVR web interface and navigate to System > Maintenance > Version or similar path to view the firmware build number; alternatively, check via SNMP or the device API if availableAffected if The firmware version is below 73.9.0.18-r2 (for UC series), below 75.9.0.18-r2 (for E series), or below 71.9.0.18-r2 (for UH series)
-
Verify if the web-based management interface is exposedConfirm the NVR HTTP/HTTPS port is reachable from untrusted networks by testing external connectivity or reviewing firewall rulesAffected if The management web interface (typically ports 80/443) is accessible from the network where the vulnerability could be exploited
-
Inspect password reset mechanism accessibilityAccess the password reset or account recovery page on the NVR web interface and verify whether the endpoint accepts unauthenticated or weakly validated requestsAffected if The password reset functionality can be triggered without prior authentication or with insufficient validation
The environment is affected if you have a Milesight NVR device from the listed series running firmware versions below the specified thresholds with the web management interface accessible to the network.
Generated from the published advisory. Verify against your own configuration.
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 · scoped71.9.0.18-r273.9.0.18-r275.9.0.18-r2
Apply the vendor-supplied firmware update to the Milesight NVR devices to remediate the weak password reset vulnerability. If no update is available, restrict network access to the management interface via firewall rules or VPN.
Upgrade to firmware version 73.9.0.18-r2 (N5008 UC, N1008 UNC, N1008 UC, N1004 UC), 75.9.0.18-r2 (N5016 E, N5008 E), or 71.9.0.18-r2 (N7016 UH, N7032 UH) depending on model
- 1. Identify the exact Milesight NVR model from the affected list (MS-Nxxxx-xxG, MS-Nxxxx-xxE, MS-Nxxxx-xxT, MS-Nxxxx-xxH, or MS-Nxxxx-xxC series).
- 2. Access the NVR web-based management interface using administrative credentials.
- 3. Navigate to the firmware/settings section to check the current firmware version.
- 4. Download the appropriate firmware update from the official Milesight website or contact Milesight support.
- 5. Upload and install the fixed firmware version: 73.9.0.18-r2 for N5008 UC, N1008 UNC, N1008 UC, N1004 UC; 75.9.0.18-r2 for N5016 E, N5008 E; 71.9.0.18-r2 for N7016 UH, N7032 UH.
- 6. Verify the firmware version after upgrade to confirm the patch was applied.
- 7. Change default administrative passwords after the upgrade as a security best practice.
- 8. Consider restricting web management interface access to trusted networks or using VPN.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30466 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-30466 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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