CVE-2023-30467
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 improper authorization 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 perform unauthorized activities 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 · moderate confidenceThis is an improper authorization vulnerability in Milesight 4K/H.265 Series NVR web management interface. A remote attacker can send specially crafted HTTP requests to bypass authentication/authorization controls and perform unauthorized administrative actions on the NVR device.
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 modelCheck the device label, web management interface system info page, or NVR diagnostics for the exact model number (e.g., N5008, N1008, N7016)Affected if The device model matches one of the affected products: N5008, N1008, N1004, N5016, N7016, or N7032
-
Check the installed firmware versionAccess the NVR web interface, navigate to System > System Info or Settings > About, and record the firmware version stringAffected if The firmware version is below 73.9.0.18-r2 for Uc variants, below 75.9.0.18-r2 for E variants, or below 71.9.0.18-r2 for Uh variants
-
Verify web management interface accessibilityAttempt to access the NVR web interface from an untrusted network or use a network scan to confirm port 80/443 is exposedAffected if The web management interface is reachable from untrusted networks (not restricted to trusted IPs only)
The environment is affected if it contains a Milesight NVR from the listed models running firmware versions below the specified thresholds, with the web interface network-accessible to untrusted sources.
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 vendor firmware updates immediately and restrict network access to the NVR web management interface to trusted sources only.
Upgrade to Milesight NVR firmware version 73.9.0.18-r2 or higher for N5008-UC/N1008-UNC/N1008-UC/N1004-UC models; 75.9.0.18-r2 or higher for N5016-E/N5008-E models; 71.9.0.18-r2 or higher for N7016-UH/N7032-UH models
- 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)
- Access the NVR web-based management interface using admin credentials
- Navigate to the System or Maintenance settings menu
- Locate the Firmware Upgrade or System Update option
- Download the appropriate firmware version from the official Milesight support website or contact vendor for the fixed release
- Upload the firmware file (73.9.0.18-r2 or higher for UC/UNC/UC models, 75.9.0.18-r2 or higher for E models, 71.9.0.18-r2 or higher for UH models)
- Allow the upgrade process to complete without powering off the device
- After reboot, verify the firmware version has been updated successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,816.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-30467 — 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-30467 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